<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jan 27, 2016 at 11:01 AM, Joop wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
><br>
> Is this problem already known? Should it be sufficent to only create<br>
> the symbolic link? What process/service is in charge to create the link?<br>
><br>
><br>
</div></div>I have that problem too once in a while. Restarting vdsmd will solve<br>
your problem BUT its because vdsmd is active before your NFS is up. A<br>
fix is to require nfs in the vdsmd service unit.<br>
<br>
Regards,<br>
<br>
Joop<br>
<br>
<br>
<br><br></blockquote><div><br></div><div>Thanks Joop,</div><div>The link was indeed created after restart of vdsmd service and I'm now able to power on the 2 VMs.</div><div>In the past I already put the require for nfs-server.service in ovirt-ha-broker.service, but I notice that actually the update to 3.6.2 overwrote it (as normally it happens for init units, I forgot it.... ;-)</div><div>So I put it again and I also put inside vdsmd.service.</div><div><br></div><div>The ovirt-ha-agent service starts after ovirt-ha-broker so it doesn't need the require line.</div></div><br></div><div class="gmail_extra">Gianluca</div></div>