On Wed, Jan 27, 2016 at 11:01 AM, Joop wrote:

>
> Is this problem already known? Should it be sufficent to only create
> the symbolic link? What process/service is in charge to create the link?
>
>

I have that problem too once in a while. Restarting vdsmd will solve
your problem BUT its because vdsmd is active before your NFS is up. A
fix is to require nfs in the vdsmd service unit.

Regards,

Joop

Thanks Joop,

The link was indeed created after restart of vdsmd service and I'm now able to power on the 2 VMs.

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.... ;-)

So I put it again and I also put inside vdsmd.service.

The ovirt-ha-agent service starts after ovirt-ha-broker so it doesn't need the require line.

Gianluca