7:05 a.m.
------=_Part_248632_1897277808.1421125514852
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi,
still working on this hosted-engine setup. =C2=A0When deploy hosted-engine =
on the 2nd node, hosted-engine.lockspace and hosted-engine.metadata cannot =
be found.
1) =C2=A0Node1 is up with hosted engine installed on a GlusterFS volume. =
=C2=A0When try to deploy hosted engine on node2, =C2=A0I specified storage =
path to be nfs available on "ovirtmount.xyz.com". =C2=A0ovirtmount 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=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0/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/.... =C2=A0 ins=
tead of "ovirtmount"=C2=A0 =C2=A0 hosted-engine-lockspace=C2=A0
=C2=A0 =C2=A0 hosted-engine-metadata
If I re-run deploy again using IP for the NFS export, the symlinks will loo=
k good and go forward with the process.
2) Then something killed the VM at this point. Sure it was running.[ INFO =
=C2=A0] Configuring VDSM[ INFO =C2=A0] Starting vdsmd[ INFO =C2=A0] Waiting=
for VDSM hardware info[ INFO =C2=A0] Waiting for VDSM hardware info[ INFO =
=C2=A0] Connected to Storage Domain[ INFO =C2=A0] Configuring VM[ INFO =C2=
=A0] Updating hosted-engine configuration[ INFO =C2=A0] Stage: Transaction =
commit[ INFO =C2=A0] Stage: Closing up[ ERROR ] Failed to execute stage 'Cl=
osing up': <urlopen error [Errno 113] No route to host>[ INFO =C2=A0] Stage=
: Clean up[ INFO =C2=A0] Generating answer file '/etc/ovirt-hosted-engine/a=
nswers.conf'[ INFO =C2=A0] Answer file '/etc/ovirt-hosted-engine/answers.co=
nf' has been updated[ INFO =C2=A0] Stage: Pre-termination[ INFO =C2=A0] Sta=
ge: Termination
Will
------=_Part_248632_1897277808.1421125514852
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff;
font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo=
nt-size:16px"><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr">Hi,</=
div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr"><br></div><div =
id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr">still working on
this ho=
sted-engine setup. When deploy hosted-engine on the 2nd node, hosted-=
engine.lockspace and hosted-engine.metadata cannot be found.</div><div id=
=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr"><br></div><div id=3D"yui_3=
_16_0_1_1421121684947_4392" dir=3D"ltr">1) Node1 is up with
hosted en=
gine installed on a GlusterFS volume. When try to deploy hosted engin=
e on node2, I specified storage path to be nfs available on "ovirtmou=
nt.xyz.com". ovirtmount is just an entry in the host file pointing to=
node1 as in the "Up and Running with oVirt 3.5".</div><div
id=3D"yui_3_16_=
0_1_1421121684947_4392" dir=3D"ltr"><br></div><div
id=3D"yui_3_16_0_1_14211=
21684947_4392" dir=3D"ltr">The deploy process mounted the ifs export
under&=
nbsp;</div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr" class=3D=
""
style=3D""> /rhev/data-center/mnt/ovirtmount.xyz.=
com:_engine/9d2142eb-f414-46f1-895a-95099aeb7f69/ha_agent</div><div
id=3D"y=
ui_3_16_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D""><br class=
=3D"" style=3D""></div><div
id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"l=
tr" class=3D"" style=3D"">I fond symlinks point to
/rhev/data-center/mnt/&l=
t;IP>:_engine/.... instead of "ovirtmount"</div><div
id=3D"yui_3_=
16_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D""> =
hosted-engine-lockspace <br></div><div
id=3D"yui_3_16_0_1_142112168494=
7_4392" dir=3D"ltr" class=3D"" style=3D"">
hosted-engine-metad=
ata<br></div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr" class=
=3D"" style=3D""><br></div><div
id=3D"yui_3_16_0_1_1421121684947_4392" dir=
=3D"ltr" class=3D"" style=3D"">If I re-run deploy again
using IP for the NF=
S export, the symlinks will look good and go forward with the process.</div=
<div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr" class=3D"" style=
=3D""><br></div><div
id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr" cla=
ss=3D"" style=3D"">2) Then something killed the VM at this point.
Sure it w=
as running.</div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr" cl=
ass=3D"" style=3D"">[ INFO ] Configuring
VDSM</div><div id=3D"yui_3_1=
6_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ INFO ] =
Starting vdsmd</div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr"=
class=3D"" style=3D"">[ INFO ] Waiting for VDSM hardware
info</div><=
div id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr"
class=3D"" style=3D"=
">[ INFO ] Waiting for VDSM hardware info</div><div
id=3D"yui_3_16_0_=
1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ INFO ] Conn=
ected to Storage Domain</div><div
id=3D"yui_3_16_0_1_1421121684947_4392" di=
r=3D"ltr" class=3D"" style=3D"">[ INFO ]
Configuring VM</div><div id=
=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ IN=
FO ] Updating hosted-engine configuration</div><div
id=3D"yui_3_16_0_=
1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ INFO ] Stag=
e: Transaction commit</div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=
=3D"ltr" class=3D"" style=3D"">[ INFO ] Stage:
Closing up</div><div i=
d=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ E=
RROR ] Failed to execute stage 'Closing up': <urlopen error [Errno 113] =
No route to host></div><div
id=3D"yui_3_16_0_1_1421121684947_4392" dir=
=3D"ltr" class=3D"" style=3D"">[ INFO ] Stage:
Clean up</div><div id=
=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ IN=
FO ] Generating answer file
'/etc/ovirt-hosted-engine/answers.conf'</=
div><div id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr"
class=3D"" styl=
e=3D"">[ INFO ] Answer file
'/etc/ovirt-hosted-engine/answers.conf' h=
as been updated</div><div id=3D"yui_3_16_0_1_1421121684947_4392"
dir=3D"ltr=
" class=3D"" style=3D"">[ INFO ] Stage:
Pre-termination</div><div id=
=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr" class=3D""
style=3D"">[ IN=
FO ] Stage: Termination</div><div class=3D""
style=3D"" id=3D"yui_3_1=
6_0_1_1421121684947_4743"><br class=3D""
style=3D""></div><div class=3D"" s=
tyle=3D"" id=3D"yui_3_16_0_1_1421121684947_4721"><br
class=3D"" style=3D"">=
</div><div id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr"
class=3D"" st=
yle=3D"">Will</div><div
id=3D"yui_3_16_0_1_1421121684947_4392" dir=3D"ltr" =
class=3D""
style=3D""><br></div></div></body></html>
------=_Part_248632_1897277808.1421125514852--
9:42 a.m.
----- Original Message -----
From: "Will K" <yetanotherwill(a)yahoo.com>
To: users(a)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
6:43 p.m.
------=_Part_520511_1303684877.1421167391436
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Let me review my ovirt-hosted-engine-setup logs and I'll see if it is related to
update the bug.
Thanks
Will
On Tuesday, January 13, 2015 2:42 AM, Yedidyah Bar David <didi(a)redhat.com>
wrote:
----- Original Message -----
From: "Will K" <yetanotherwill(a)yahoo.com>
To: users(a)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
------=_Part_520511_1303684877.1421167391436
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff;
font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo=
nt-size:16px"><div id=3D"yui_3_16_0_1_1421081331210_236916">Let me
review m=
y ovirt-hosted-engine-setup logs and I'll see if it is related to update th=
e bug.</div><div
id=3D"yui_3_16_0_1_1421081331210_236918"><br></div><div id=
=3D"yui_3_16_0_1_1421081331210_236920"
dir=3D"ltr">Thanks<br>Will<br></div>=
<div
id=3D"yui_3_16_0_1_1421081331210_236906"><span></span></div>
<div clas=
s=3D"qtdSeparateBR"><br><br></div><div
style=3D"display: block;" class=3D"y=
ahoo_quoted"> <div style=3D"font-family: HelveticaNeue, Helvetica Neue,
Hel=
vetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div
style=3D"=
font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande=
, sans-serif; font-size: 16px;"> <div dir=3D"ltr"> <font
size=3D"2" face=3D=
"Arial"> On Tuesday, January 13, 2015 2:42 AM, Yedidyah Bar David
<didi@=
redhat.com> wrote:<br> </font> </div> <br><br>
<div class=3D"y_msg_cont=
ainer">----- Original Message -----<br clear=3D"none">>
From: "Will K" &=
lt;<a shape=3D"rect" ymailto=3D"mailto:yetanotherwill@yahoo.com"
href=3D"ma=
ilto:yetanotherwill@yahoo.com">yetanotherwill@yahoo.com</a>><br
clear=3D=
"none">> To: <a shape=3D"rect"
ymailto=3D"mailto:users@ovirt.org" href=
=3D"mailto:users@ovirt.org">users@ovirt.org</a><br
clear=3D"none">> Sent=
: Tuesday, January 13, 2015 7:05:14 AM<br clear=3D"none">> Subject:
[ovi=
rt-users] hosted-engine-lockspace broken symlinks<br
clear=3D"none">> <b=
r clear=3D"none">> Hi,<br clear=3D"none">>
<br clear=3D"none">> st=
ill working on this hosted-engine setup. When deploy hosted-engine on the<b=
r clear=3D"none">> 2nd node, hosted-engine.lockspace and
hosted-engine.m=
etadata cannot be<br clear=3D"none">> found.<br
clear=3D"none">> <br =
clear=3D"none">> 1) Node1 is up with hosted engine installed on a
Gluste=
rFS volume. When try<br clear=3D"none">> to deploy hosted engine on
node=
2, I specified storage path to be nfs<br clear=3D"none">> available
on "=
ovirtmount.xyz.com". ovirtmount is just an entry in the host<br clear=3D"no=
ne">> file pointing to node1 as in the "Up and Running with oVirt
3.5".<=
br clear=3D"none">> <br clear=3D"none">> The
deploy process mounted t=
he ifs export under<br clear=3D"none">>
/rhev/data-center/mnt/ovirtmount=
.xyz.com:_engine/9d2142eb-f414-46f1-895a-95099aeb7f69/ha_agent<br clear=3D"=
none">> <br clear=3D"none">> I fond symlinks point
to /rhev/data-cent=
er/mnt/<IP>:_engine/.... instead of<br
clear=3D"none">> "ovirtmoun=
t"<br clear=3D"none">> hosted-engine-lockspace<br
clear=3D"none">> ho=
sted-engine-metadata<br clear=3D"none">> <br
clear=3D"none">> If I re=
-run deploy again using IP for the NFS export, the symlinks will look<br cl=
ear=3D"none">> good and go forward with the process.<br
clear=3D"none"><=
br clear=3D"none">IMO if you always supplied a name (even if resolvable onl=
y by /etc/hosts) and<br clear=3D"none">not an IP address, the mounts
should=
always use the name. We have a different<br clear=3D"none">bug [1] which
s=
eems similar, but is related to the name of the host, not of<br clear=3D"no=
ne">the nfs server.<br clear=3D"none"><br
clear=3D"none">Can you please pos=
t setup logs of all of the hosts?<br
clear=3D"none">/var/log/ovirt-hosted-e=
ngine-setup/*<br clear=3D"none"><br clear=3D"none">[1]
<a shape=3D"rect" hr=
ef=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1178535"
target=3D"_bla=
nk">https://bugzilla.redhat.com/show_bug.cgi?id=3D1178535</a&g...
class=3D"=
yqt1495211211" id=3D"yqtfd71261"><br
clear=3D"none"><br clear=3D"none">>=
<br clear=3D"none">> 2) Then something killed the VM at this
point. Sur=
e it was running.<br clear=3D"none">> [ INFO ] Configuring
VDSM<br clear=
=3D"none">> [ INFO ] Starting vdsmd<br
clear=3D"none">> [ INFO ] Wait=
ing for VDSM hardware info<br clear=3D"none">> [ INFO ] Waiting for
VDSM=
hardware info<br clear=3D"none">> [ INFO ] Connected to Storage
Domain<=
br clear=3D"none">> [ INFO ] Configuring VM<br
clear=3D"none">> [ INF=
O ] Updating hosted-engine configuration<br clear=3D"none">> [ INFO
] St=
age: Transaction commit<br clear=3D"none">> [ INFO ] Stage: Closing
up<b=
r clear=3D"none">> [ ERROR ] Failed to execute stage 'Closing
up': <u=
rlopen error [Errno 113] No<br clear=3D"none">> route to
host></div><=
br clear=3D"none"><br clear=3D"none">These logs will help
here too.<br clea=
r=3D"none"><br clear=3D"none">Thanks,<br
clear=3D"none">-- <br clear=3D"non=
e">Didi<div class=3D"yqt1495211211"
id=3D"yqtfd27853"><br clear=3D"none"></=
div><br><br></div> </div> </div> </div>
</div></body></html>
------=_Part_520511_1303684877.1421167391436--
3602
days inactive
3602
days old
2 comments
2 participants
participants (2)
-
Will K -
Yedidyah Bar David