[ovirt-users] hosted-engine-lockspace broken symlinks

[Yedidyah Bar David]

----- Original Message -----
> From: "Will K" <yetanotherwill at yahoo.com>
> To: users at ovirt.org
> Sent: Tuesday, January 13, 2015 7:05:14 AM
> Subject: [ovirt-users] hosted-engine-lockspace broken symlinks
> 
> Hi,
> 
> still working on this hosted-engine setup. When deploy hosted-engine on the
> 2nd node, hosted-engine.lockspace and hosted-engine.metadata cannot be
> found.
> 
> 1) Node1 is up with hosted engine installed on a GlusterFS volume. When try
> to deploy hosted engine on node2, I specified storage path to be nfs
> available on "ovirtmount.xyz.com". ovirtmount is just an entry in the host
> file pointing to node1 as in the "Up and Running with oVirt 3.5".
> 
> The deploy process mounted the ifs export under
> /rhev/data-center/mnt/ovirtmount.xyz.com:_engine/9d2142eb-f414-46f1-895a-95099aeb7f69/ha_agent
> 
> I fond symlinks point to /rhev/data-center/mnt/<IP>:_engine/.... instead of
> "ovirtmount"
> hosted-engine-lockspace
> hosted-engine-metadata
> 
> If I re-run deploy again using IP for the NFS export, the symlinks will look
> good and go forward with the process.

IMO if you always supplied a name (even if resolvable only by /etc/hosts) and
not an IP address, the mounts should always use the name. We have a different
bug [1] which seems similar, but is related to the name of the host, not of
the nfs server.

Can you please post setup logs of all of the hosts?
/var/log/ovirt-hosted-engine-setup/*

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1178535

> 
> 2) Then something killed the VM at this point. Sure it was running.
> [ INFO ] Configuring VDSM
> [ INFO ] Starting vdsmd
> [ INFO ] Waiting for VDSM hardware info
> [ INFO ] Waiting for VDSM hardware info
> [ INFO ] Connected to Storage Domain
> [ INFO ] Configuring VM
> [ INFO ] Updating hosted-engine configuration
> [ INFO ] Stage: Transaction commit
> [ INFO ] Stage: Closing up
> [ ERROR ] Failed to execute stage 'Closing up': <urlopen error [Errno 113] No
> route to host>

These logs will help here too.

Thanks,
-- 
Didi