<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1421081331210_236916">Let me review my ovirt-hosted-engine-setup logs and I'll see if it is related to update the bug.</div><div id="yui_3_16_0_1_1421081331210_236918"><br></div><div id="yui_3_16_0_1_1421081331210_236920" dir="ltr">Thanks<br>Will<br></div><div id="yui_3_16_0_1_1421081331210_236906"><span></span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font size="2" face="Arial"> On Tuesday, January 13, 2015 2:42 AM, Yedidyah Bar David <didi@redhat.com> wrote:<br> </font> </div> <br><br> <div class="y_msg_container">----- Original Message -----<br clear="none">> From: "Will K" <<a shape="rect" ymailto="mailto:yetanotherwill@yahoo.com" href="mailto:yetanotherwill@yahoo.com">yetanotherwill@yahoo.com</a>><br clear="none">> To: <a shape="rect" ymailto="mailto:users@ovirt.org" href="mailto:users@ovirt.org">users@ovirt.org</a><br clear="none">> Sent: Tuesday, January 13, 2015 7:05:14 AM<br clear="none">> Subject: [ovirt-users] hosted-engine-lockspace broken symlinks<br clear="none">> <br clear="none">> Hi,<br clear="none">> <br clear="none">> still working on this hosted-engine setup. When deploy hosted-engine on the<br clear="none">> 2nd node, hosted-engine.lockspace and hosted-engine.metadata cannot be<br clear="none">> found.<br clear="none">> <br clear="none">> 1) Node1 is up with hosted engine installed on a GlusterFS volume. When try<br clear="none">> to deploy hosted engine on node2, I specified storage path to be nfs<br clear="none">> available on "ovirtmount.xyz.com". ovirtmount is just an entry in the host<br clear="none">> file pointing to node1 as in the "Up and Running with oVirt 3.5".<br clear="none">> <br clear="none">> The deploy process mounted the ifs export under<br clear="none">> /rhev/data-center/mnt/ovirtmount.xyz.com:_engine/9d2142eb-f414-46f1-895a-95099aeb7f69/ha_agent<br clear="none">> <br clear="none">> I fond symlinks point to /rhev/data-center/mnt/<IP>:_engine/.... instead of<br clear="none">> "ovirtmount"<br clear="none">> hosted-engine-lockspace<br clear="none">> hosted-engine-metadata<br clear="none">> <br clear="none">> If I re-run deploy again using IP for the NFS export, the symlinks will look<br clear="none">> good and go forward with the process.<br clear="none"><br clear="none">IMO if you always supplied a name (even if resolvable only by /etc/hosts) and<br clear="none">not an IP address, the mounts should always use the name. We have a different<br clear="none">bug [1] which seems similar, but is related to the name of the host, not of<br clear="none">the nfs server.<br clear="none"><br clear="none">Can you please post setup logs of all of the hosts?<br clear="none">/var/log/ovirt-hosted-engine-setup/*<br clear="none"><br clear="none">[1] <a shape="rect" href="https://bugzilla.redhat.com/show_bug.cgi?id=1178535" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1178535</a><div class="yqt1495211211" id="yqtfd71261"><br clear="none"><br clear="none">> <br clear="none">> 2) Then something killed the VM at this point. Sure it was running.<br clear="none">> [ INFO ] Configuring VDSM<br clear="none">> [ INFO ] Starting vdsmd<br clear="none">> [ INFO ] Waiting for VDSM hardware info<br clear="none">> [ INFO ] Waiting for VDSM hardware info<br clear="none">> [ INFO ] Connected to Storage Domain<br clear="none">> [ INFO ] Configuring VM<br clear="none">> [ INFO ] Updating hosted-engine configuration<br clear="none">> [ INFO ] Stage: Transaction commit<br clear="none">> [ INFO ] Stage: Closing up<br clear="none">> [ ERROR ] Failed to execute stage 'Closing up': <urlopen error [Errno 113] No<br clear="none">> route to host></div><br clear="none"><br clear="none">These logs will help here too.<br clear="none"><br clear="none">Thanks,<br clear="none">-- <br clear="none">Didi<div class="yqt1495211211" id="yqtfd27853"><br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>