6:58 a.m.
This is a message in Mime Format. If you see this, your mail reader does not support this
format.
--=_5a5100e4d4e925f5636c71273e699e07
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
After upgrade of vdsm from 4.9.6-0.196.gitb8b79b5 to 4.9.6-0.201.git98e=
8078=0A=0Aengine set host in nonoperational mode, the error is=0A=0A"Hos=
t kvm04 is compatible with versions (3.0,3.1) and cannot join Cluster De=
fault which is set to version 3.1."=0A=0A--
--=_5a5100e4d4e925f5636c71273e699e07
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
After upgrade of vdsm from 4.9.6-0.196.gitb8b79b5 to 4.9.6-0.201.g=
it98e8078<br><br>engine set host in nonoperational mode, the error is<br=
<br><br><div title=3D""
style=3D"outline: medium none;"><div id=3D"gwt-=
uid-1204_col2_row6">"Host kvm04 is compatible with versions (3.0,3.1)
an=
d cannot join Cluster Default which is set to version
3.1."</div></div><=
br><br>--<br><br>
--=_5a5100e4d4e925f5636c71273e699e07--
7:24 a.m.
--=_b1467d5a-fee9-4f54-a9dc-53e673ab99e0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
I guess you compiled vdsm yourself, please run the following command from your host:
vdsClient -s 0 getVdsCaps (assuming you work with SSL).
anyhow, it smells like a known issue with latest build where vdsm returns
supported_clusters = 3.0 and engine reject host, but lets find out.
Thanks,
Haim
----- Original Message -----
From: ovirt(a)qip.ru
To: users(a)ovirt.org
Sent: Wednesday, May 16, 2012 1:58:33 PM
Subject: [Users] Host can't join the cluster
After upgrade of vdsm from 4.9.6-0.196.gitb8b79b5 to
4.9.6-0.201.git98e8078
engine set host in nonoperational mode, the error is
"Host kvm04 is compatible with versions (3.0,3.1) and cannot
join
Cluster Default which is set to version 3.1."
--
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--=_b1467d5a-fee9-4f54-a9dc-53e673ab99e0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><style type=3D'text/css'>p { margin: 0;
}</style></head><body><=
div style=3D'font-family: Arial; font-size: 10pt; color: #000000'><font
siz=
e=3D"2" face=3D"arial, helvetica, sans-serif">I guess you compiled
vdsm you=
rself, please run the following command from your host:</font><div st=
yle=3D"color: rgb(0, 0, 0); "><font face=3D"arial, helvetica,
sans-serif" s=
ize=3D"2"><br></font></div><div style=3D"color:
rgb(0, 0, 0); "><font face=
=3D"arial, helvetica, sans-serif" size=3D"2">vdsClient -s 0
getVdsCaps (ass=
uming you work with SSL). </font></div><div style=3D"color:
rgb(0, 0, =
0); "><font face=3D"arial, helvetica, sans-serif"
size=3D"2"><br></font></d=
iv><div><font face=3D"arial, helvetica, sans-serif"
size=3D"2">anyhow, it&n=
bsp;smells like a known issue with latest build where vdsm returns sup=
ported_clusters =3D 3.0 and engine reject host, but lets find out. </f=
ont></div><div><font size=3D"2" face=3D"arial, helvetica,
sans-serif"><br><=
/font></div><div><font size=3D"2" face=3D"arial,
helvetica, sans-serif">Tha=
nks, </font></div><div><font size=3D"2"
face=3D"arial, helvetica, sans=
-serif"><br></font></div><div><font
size=3D"2" face=3D"arial, helvetica, sa=
ns-serif">Haim</font></div><div><br><hr
id=3D"zwchr" style=3D"color: rgb(0,=
0, 0); font-family: Arial; font-size: 10pt; "><blockquote
style=3D"border-=
left-width: 2px; border-left-style: solid; border-left-color: rgb(16, 16, 2=
55); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight:=
normal; font-style: normal; text-decoration: none; font-family: Helvetica,=
Arial, sans-serif; font-size: 12pt; "><b>From:
</b>ovirt(a)qip.ru<br><b>To: =
</b>users(a)ovirt.org<br><b>Sent: </b>Wednesday, May 16, 2012
1:58:33 PM<br><=
b>Subject: </b>[Users] Host can't join the cluster<br><br>After
upgrade of =
vdsm from 4.9.6-0.196.gitb8b79b5 to
4.9.6-0.201.git98e8078<br><br>eng=
ine set host in nonoperational mode, the error is<br><br><br><div
title=3D"=
" style=3D"outline: medium none;"><div
id=3D"gwt-uid-1204_col2_row6">"Host =
kvm04 is compatible with versions (3.0,3.1) and cannot join Cluster Default=
which is set to version
3.1."</div></div><br><br>--<br><br>
<br>_______________________________________________<br>Users mailing
list<b=
r>Users@ovirt.org<br>http://lists.ovirt.org/mailman/listinfo/users<br></blo=
ckquote><br></div></div></body></html>
--=_b1467d5a-fee9-4f54-a9dc-53e673ab99e0--
8:19 a.m.
New subject: [Users] Host can't join the cluster
This is a message in Mime Format. If you see this, your mail reader does not support this
format.
--=_0ea6c1b639fdef4efc7aa62f8b477b18
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
in secure and non secure connections i have the same nonoperational stat=
us=0A=0Athe output of getVdsCaps on host is empty=0A=0Athis is event log=
in webadmin=0A=0A2012-May-16, 16:05:04Host kvm04 is compatible with ver=
sions (3.0,3.1) and cannot join Cluster Default which is set to version=
3.1.2012-May-16, 16:05:04Detected new Host kvm04. Host state was set to=
Up.2012-May-16, 16:05:03Host kvm04 was autorecovered.2012-May-16, 16:05=
:03Host kvm04 is compatible with versions (3.0,3.1) and cannot join Clus=
ter Default which is set to version 3.1.2012-May-16, 16:01:02Host kvm04=
was activated by admin(a)internal.=0Aif i do downgrade to 4.9.6-0.196.git=
b8b79b5 host state set's to Up.=0A=0A=D0=A1=D1=80=D0=B4 16 =D0=9C=D0=B0=
=D0=B9 2012 15:24:36 +0400, Haim Ateya =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=
=D0=B0=D0=BB:=0AI guess you compiled vdsm yourself, please run the foll=
owing command from your host:=0AvdsClient -s 0 getVdsCaps (assuming you=
work with SSL). =0Aanyhow, it smells like a known issue with latest bui=
ld where vdsm returns supported_clusters =3D 3.0 and engine reject host,=
but lets find out. =0AThanks, =0AHaim=0AFrom: ovirt(a)qip.ru=0ATo: users@=
ovirt.org=0ASent: Wednesday, May 16, 2012 1:58:33 PM=0ASubject: [Users]=
Host can't join the cluster=0A=0AAfter upgrade of vdsm from 4.9.6-0.19=
6.gitb8b79b5 to 4.9.6-0.201.git98e8078=0A=0Aengine set host in nonoperat=
ional mode, the error is=0A=0A"Host kvm04 is compatible with versions (3=
.0,3.1) and cannot join Cluster Default which is set to version 3.1."=0A=
=0A--=0A=0A_______________________________________________=0AUsers maili=
ng list=0AUsers@ovirt.org=0Ahttp://lists.ovirt.org/mailman/listinfo/user=
s=0A=0A--
--=_0ea6c1b639fdef4efc7aa62f8b477b18
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
in secure and non secure connections i have the same nonoperationa=
l status<br><br>the output of <font face=3D"arial, helvetica,
sans-serif=
" size=3D"2">getVdsCaps on host </font>is empty
<br><br><br>this is even=
t log in webadmin<br><br><table class=3D"GI4LN0DAFB"
__gwtcellbasedwidge=
timpldispatchingblur=3D"true" __gwtcellbasedwidgetimpldispatchingfocus=
=3D"true" cellspacing=3D"0"><tbody><tr
class=3D"GI4LN0DJDB"><td class=3D=
"GI4LN0DIDB GI4LN0DKDB GI4LN0DLDB"><div
style=3D"outline:none;"><div sty=
le=3D"line-height: 100%; text-align: center; vertical-align: middle;"><i=
mg src=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.gif" sty=
le=3D"width: 14px; height: 12px; background: url(data:image/gif;base64,R=
0lGODlhDgAMAJEDAMwzAP8zAGYAAP///yH5BAEAAAMALAAAAAAOAAwAAAIs3GA5ogeYQGBGy=
ADlo+u+gHHVBQJiYpVnBJaN4XmNJ6QYG45uZypWX1nVEgUAOw=3D=3D) no-repeat 0px 0=
px" border=3D"0"></div></div></td><td
class=3D"GI4LN0DIDB GI4LN0DKDB"><d=
iv title=3D"" style=3D"outline: medium none;"><div
id=3D"gwt-uid-1182_co=
l1_row0">2012-May-16, 16:05:04</div></div></td><td
class=3D"GI4LN0DIDB G=
I4LN0DKDB GI4LN0DFEB"><div title=3D"" style=3D"outline: medium
none;"><d=
iv id=3D"gwt-uid-1182_col2_row0">Host kvm04 is compatible with versions=
(3.0,3.1) and cannot join Cluster Default which is set to version 3.1.<=
/div></div></td></tr><tr class=3D"GI4LN0DJEB"><td
class=3D"GI4LN0DIDB GI=
4LN0DKEB GI4LN0DLDB"><div style=3D"outline:none;"><div
style=3D"line-hei=
ght: 100%; text-align: center; vertical-align: middle;"><img src=3D"http=
://engine-test:8080/webadmin/webadmin/clear.cache.gif" style=3D"width: 1=
4px; height: 12px; background: url(data:image/gif;base64,R0lGODlhDgAMAKI=
HAE3SEhlQAGHwKiYmJje5BqL/olXgG////yH5BAEAAAcALAAAAAAOAAwAAAM0eLp8ES2GAmB=
UUxArizDbMQxMBkIDUZCOdypDIY8eEMKAIMiGzeG63q0xABiHkRTyMvgxEgA7) no-repeat=
0px 0px" border=3D"0"></div></div></td><td
class=3D"GI4LN0DIDB GI4LN0DK=
EB"><div title=3D"" style=3D"outline: medium
none;"><div id=3D"gwt-uid-1=
182_col1_row1">2012-May-16, 16:05:04</div></div></td><td
class=3D"GI4LN0=
DIDB GI4LN0DKEB GI4LN0DFEB"><div title=3D"" style=3D"outline:
medium non=
e;"><div id=3D"gwt-uid-1182_col2_row1">Detected new Host kvm04.
Host sta=
te was set to Up.</div></div></td></tr><tr
class=3D"GI4LN0DJDB GI4LN0DAE=
B"><td class=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DLDB
GI4LN0DBEB"><div style=
=3D"outline:none;"><div style=3D"line-height: 100%; text-align:
center;=
vertical-align: middle;"><img src=3D"http://engine-test:8080/webadmin/w=
ebadmin/clear.cache.gif" style=3D"width: 14px; height: 12px; background:=
url(data:image/gif;base64,R0lGODlhDgAMAKIHAE3SEhlQAGHwKiYmJje5BqL/olXgG=
////yH5BAEAAAcALAAAAAAOAAwAAAM0eLp8ES2GAmBUUxArizDbMQxMBkIDUZCOdypDIY8eE=
MKAIMiGzeG63q0xABiHkRTyMvgxEgA7) no-repeat 0px 0px"
border=3D"0"></div><=
/div></td><td class=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DBEB"><div
title=3D""=
style=3D"outline: medium none;"><div
id=3D"gwt-uid-1182_col1_row2">2012=
-May-16, 16:05:03</div></div></td><td class=3D"GI4LN0DIDB
GI4LN0DKDB GI4=
LN0DFEB GI4LN0DBEB"><div title=3D"" style=3D"outline: medium
none;"><div=
id=3D"gwt-uid-1182_col2_row2">Host kvm04 was
autorecovered.</div></div>=
</td></tr><tr class=3D"GI4LN0DJEB"><td
class=3D"GI4LN0DIDB GI4LN0DKEB GI=
4LN0DLDB"><div style=3D"outline:none;"><div
style=3D"line-height: 100%;=
text-align: center; vertical-align: middle;"><img src=3D"http://engine-=
test:8080/webadmin/webadmin/clear.cache.gif" style=3D"width: 14px; heigh=
t: 12px; background: url(data:image/gif;base64,R0lGODlhDgAMAJEDAMwzAP8zA=
GYAAP///yH5BAEAAAMALAAAAAAOAAwAAAIs3GA5ogeYQGBGyADlo+u+gHHVBQJiYpVnBJaN4=
XmNJ6QYG45uZypWX1nVEgUAOw=3D=3D) no-repeat 0px 0px"
border=3D"0"></div><=
/div></td><td class=3D"GI4LN0DIDB GI4LN0DKEB"><div
title=3D"" style=3D"o=
utline: medium none;" tabindex=3D"0"><div
id=3D"gwt-uid-1182_col1_row3">=
2012-May-16, 16:05:03</div></div></td><td class=3D"GI4LN0DIDB
GI4LN0DKEB=
GI4LN0DFEB"><div title=3D"" style=3D"outline: medium
none;"><div id=3D"=
gwt-uid-1182_col2_row3">Host kvm04 is compatible with versions (3.0,3.1)=
and cannot join Cluster Default which is set to version 3.1.</div></div=
</td></tr><tr class=3D"GI4LN0DJDB"><td
class=3D"GI4LN0DIDB GI4LN0DKDB G=
I4LN0DLDB"><div
style=3D"outline:none;"><div style=3D"line-height: 100%;=
text-align: center; vertical-align: middle;"><img src=3D"http://engine-=
test:8080/webadmin/webadmin/clear.cache.gif" style=3D"width: 14px; heigh=
t: 12px; background: url(data:image/gif;base64,R0lGODlhDgAMAKIHAE3SEhlQA=
GHwKiYmJje5BqL/olXgG////yH5BAEAAAcALAAAAAAOAAwAAAM0eLp8ES2GAmBUUxArizDbM=
QxMBkIDUZCOdypDIY8eEMKAIMiGzeG63q0xABiHkRTyMvgxEgA7) no-repeat 0px 0px"=
border=3D"0"></div></div></td><td
class=3D"GI4LN0DIDB GI4LN0DKDB"><div=
style=3D"outline:none;"><div
id=3D"gwt-uid-1182_col1_row4">2012-May-16,=
16:01:02</div></div></td><td class=3D"GI4LN0DIDB GI4LN0DKDB
GI4LN0DFEB"=
<div title=3D"" style=3D"outline: medium
none;"><div id=3D"gwt-uid-1182=
_col2_row4">Host kvm04 was
activated by admin(a)internal.</div></div></td>=
</tr></tbody></table><br>if i do downgrade to
4.9.6-0.196.gitb8b79b5 hos=
t state set's to Up.<br><br><br><br><br><font
color=3D"#666">=D0=A1=D1=
=80=D0=B4 16 =D0=9C=D0=B0=D0=B9 2012 15:24:36 +0400, Haim Ateya <hate=
ya(a)redhat.com&gt; =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:</font><br>=
<blockquote style=3D"padding-left:10px; margin:10px 10px 10px 0px; borde=
r-left:#aaa 2px dotted"><div style=3D"font-family: Arial; font-size: 10p=
t; color: #000000"><font face=3D"arial, helvetica, sans-serif"
size=3D"2=
">I guess you compiled vdsm yourself, please run the following com=
mand from your host:</font><div style=3D"color: rgb(0, 0, 0);
"><font fa=
ce=3D"arial, helvetica, sans-serif"
size=3D"2"><br></font></div><div sty=
le=3D"color: rgb(0, 0, 0); "><font face=3D"arial, helvetica,
sans-serif"=
size=3D"2">vdsClient -s 0 getVdsCaps (assuming you work with
SSL). =
;</font></div><div style=3D"color: rgb(0, 0, 0); "><font
face=3D"arial,=
helvetica, sans-serif"
size=3D"2"><br></font></div><div><font
face=3D"a=
rial, helvetica, sans-serif" size=3D"2">anyhow,
it smells like=
a known issue with latest build where vdsm returns supported_clusters=
=3D 3.0 and engine reject host, but lets find
out. </font></div><d=
iv><font face=3D"arial, helvetica, sans-serif"
size=3D"2"><br></font></d=
iv><div><font face=3D"arial, helvetica, sans-serif"
size=3D"2">Thanks,&n=
bsp;</font></div><div><font face=3D"arial, helvetica,
sans-serif" size=
=3D"2"><br></font></div><div><font
face=3D"arial, helvetica, sans-serif"=
size=3D"2">Haim</font></div><div><br><hr
xsscleaned=3D"zwchr" style=3D"=
color: rgb(0, 0, 0); font-family: Arial; font-size: 10pt; "><blockquote=
style=3D"border-left-width: 2px; border-left-style: solid; border-left-=
color: rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb=
(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: non=
e; font-family: Helvetica, Arial, sans-serif; font-size: 12pt; "><b>From=
: </b>ovirt(a)qip.ru<br><b>To:
</b>users(a)ovirt.org<br><b>Sent: </b>Wednesd=
ay, May 16, 2012 1:58:33 PM<br><b>Subject: </b>[Users] Host can't
join t=
he cluster<br><br>After upgrade of vdsm from 4.9.6-0.196.gitb8b79b=
5 to 4.9.6-0.201.git98e8078<br><br>engine set host in nonoperational mod=
e, the error is<br><br><br><div title=3D""
style=3D"outline: medium none=
;"><div xsscleaned=3D"gwt-uid-1204_col2_row6">"Host kvm04 is
compatible=
with versions (3.0,3.1) and cannot join Cluster Default which is set to=
version
3.1."</div></div><br><br>--<br><br>=0D=0A<br>__________________=
_____________________________<br>Users mailing list<br>Users(a)ovirt.org<b=
r><a style=3D"border-bottom:1px dotted; text-decoration: none" target=3D=
"_blank" href=3D"http://lists.ovirt.org/mailman/listinfo/users"
title=3D=
"=D0=9E=D1=82=D0=BA=D1=80=D1=8B=D1=82=D1=8C =D0=B2=D0=BD=D0=B5=D1=88=D0=
=BD=D1=8E=D1=8E =D1=81=D1=81=D1=8B=D0=BB=D0=BA=D1=83">http://lists.ovirt=
.org/mailman/listinfo/users</a><br></blockquote><br></div></div>=0D=0A</=
blockquote><br><br>--<br>=0D=0A<br>
--=_0ea6c1b639fdef4efc7aa62f8b477b18--
9:59 a.m.
New subject: [Users] Host can't join the cluster
--=_ef2cb314-a01b-4313-84f2-4a7c34d7baaf
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
This issue was introduced in Ic7b4a63a974bfc301f3294603d8fe91f534b74dd (htt=
p://gerrit.ovirt.org/4284), we are currently working to resolve this issue =
and patch will be sent soon.
meantime, you can edit /usr/share/vdsm/dsaversion.py and change the followi=
ng fields:
software_version =3D "4.9"
software_revision =3D "0
restart vdsmd service and activate host again.
Haim
----- Original Message -----
> > vdsClient -s 0 getVdsCaps (assuming you work with SSL).
> > anyhow, it smells like a known issue with latest build where vdsm
> > returns supported_clusters =3D 3.0 and engine reject host, but lets
> > find out.
> > Thanks,
> > Haim
> > > From: ovirt(a)qip.ru
> > > > To: users(a)ovirt.org
> > > > Sent: Wednesday, May
16, 2012 1:58:33 PM
> > > > Subject: [Users]
Host can't join the cluster
>
> > > After upgrade of vdsm from 4.9.6-0.196.gitb8b79b5 to
> > > 4.9.6-0.201.git98e8078
>
> > > engine set host in nonoperational mode, the error is
>
> > > "Host kvm04 is compatible with versions (3.0,3.1) and cannot join
> > > Cluster Default which is set to version 3.1."
>
> >
> > > _______________________________________________
> > > > Users mailing list
> > > > Users(a)ovirt.org
> > > >
http://lists.ovirt.org/mailman/listinfo/users
>
From: ovirt(a)qip.ru
To: "Haim Ateya" <hateya(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Wednesday, May 16, 2012 3:19:04 PM
Subject: Re: Re: [Users] Host can't jo=C2=ADin the cluster
in secure and non secure connections i have the same nonoperational
status
the output of getVdsCaps on host is empty
this is event log in webadmin
2012-May-16, 16:05:04
Host kvm04 is compatible with versions (3.0,3.1) and cannot join
Cluster Default which is set to version 3.1.
2012-May-16, 16:05:04
Detected new Host kvm04. Host state was set to Up.
2012-May-16, 16:05:03
Host kvm04 was autorecovered.
2012-May-16, 16:05:03
Host kvm04 is compatible with versions (3.0,3.1) and cannot join
Cluster Default which is set to version 3.1.
2012-May-16, 16:01:02
Host kvm04 was activated by admin@internal.
if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to Up.
=D0=A1=D1=80=D0=B4 16 =D0=9C=D0=B0=D0=B9 2012 15:24:36 +0400, Haim
Ateya =
<hateya(a)redhat.com>
=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
> > I guess you compiled vdsm yourself, please run the following
> > command
> > from your host:
--
> --
--=_ef2cb314-a01b-4313-84f2-4a7c34d7baaf
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><style type=3D'text/css'>p { margin: 0;
}</style></head><body><=
div style=3D'font-family: Arial; font-size: 10pt; color: #000000'><font
fac=
e=3D"Arial" size=3D"2">This issue was introduced in
Ic7b4a63a974bfc301f3294=
603d8fe91f534b74dd (http://gerrit.ovirt.org/4284), we are currently working=
to resolve this issue</font><div style=3D"color: rgb(0, 0, 0);
font-family=
: Arial; font-size: 10pt; ">and patch will be sent
soon. </div><div st=
yle=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 10pt; ">meantime=
, you can edit /usr/share/vdsm/dsaversion.py and change the following field=
s:</div><div><div style=3D"color: rgb(0, 0, 0); font-family: Arial;
font-si=
ze: 10pt; ">software_version =3D "4.9"</div><div
style=3D"color: rgb(0, 0, =
0); font-family: Arial; font-size: 10pt; ">software_revision =3D
"0</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 10pt;
"><br=
</div><div style=3D"color: rgb(0, 0, 0); font-family:
Arial; font-size: 10=
pt; ">restart vdsmd service and activate host
again. </div><div style=
=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 10pt;
"><br></div><=
div style=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 10pt; ">Ha=
im</div><br><hr id=3D"zwchr" style=3D"color: rgb(0, 0, 0);
font-family: Ari=
al; font-size: 10pt; "><blockquote style=3D"border-left-width: 2px;
border-=
left-style: solid; border-left-color: rgb(16, 16, 255); margin-left: 5px; p=
adding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: nor=
mal; text-decoration: none; font-family: Helvetica, Arial, sans-serif; font=
-size: 12pt; "><b>From: </b>ovirt(a)qip.ru<br><b>To:
</b>"Haim Ateya" <hat=
eya(a)redhat.com&gt;<br><b>Cc:
</b>users(a)ovirt.org<br><b>Sent: </b>Wednesday,=
May 16, 2012 3:19:04 PM<br><b>Subject: </b>Re: Re: [Users] Host
can't jo=
=C2=ADin the cluster<br><br><link rel=3D"stylesheet"
href=3D"/zimbra/css/ms=
gview.css?v=3D110804122015"> in secure and non secure connections i ha=
ve the same nonoperational status<br><br>the output of <font
face=3D"arial,=
helvetica, sans-serif" size=3D"2">getVdsCaps on host </font>is
empty <br><=
br><br>this is event log in webadmin<br><br><table
class=3D"GI4LN0DAFB" cel=
lspacing=3D"0"><tbody><tr class=3D"GI4LN0DJDB"><td
class=3D"GI4LN0DIDB GI4L=
N0DKDB GI4LN0DLDB"><div style=3D"outline:none;"><div
style=3D"line-height: =
100%; text-align: center; vertical-align: middle;"><img style=3D"width:
14p=
x; height: 12px; background: none no-repeat 0px 0px" border=3D"0"
src=3D"ht=
tp://engine-test:8080/webadmin/webadmin/clear.cache.gif" src=3D"http://engi=
ne-test:8080/webadmin/webadmin/clear.cache.gif"></div></div></td><td
class=
=3D"GI4LN0DIDB GI4LN0DKDB"><div title=3D""
style=3D"outline: medium none;">=
<div id=3D"gwt-uid-1182_col1_row0">2012-May-16,
16:05:04</div></div></td><t=
d class=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DFEB"><div title=3D""
style=3D"outli=
ne: medium none;"><div id=3D"gwt-uid-1182_col2_row0">Host kvm04 is
compatib=
le with versions (3.0,3.1) and cannot join Cluster Default which is set to =
version 3.1.</div></div></td></tr><tr
class=3D"GI4LN0DJEB"><td class=3D"GI4=
LN0DIDB GI4LN0DKEB GI4LN0DLDB"><div
style=3D"outline:none;"><div style=3D"l=
ine-height: 100%; text-align: center; vertical-align: middle;"><img style=
=3D"width: 14px; height: 12px; background: none no-repeat 0px 0px" border=
=3D"0"
src=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.gif" sr=
c=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.gif"></div></div=
</td><td class=3D"GI4LN0DIDB GI4LN0DKEB"><div
title=3D"" style=3D"outline:=
medium none;"><div
id=3D"gwt-uid-1182_col1_row1">2012-May-16, 16:05:04</di=
v></div></td><td class=3D"GI4LN0DIDB GI4LN0DKEB
GI4LN0DFEB"><div title=3D""=
style=3D"outline: medium none;"><div
id=3D"gwt-uid-1182_col2_row1">Detecte=
d new Host kvm04. Host state was set to
Up.</div></div></td></tr><tr class=
=3D"GI4LN0DJDB GI4LN0DAEB"><td class=3D"GI4LN0DIDB GI4LN0DKDB
GI4LN0DLDB GI=
4LN0DBEB"><div style=3D"outline:none;"><div
style=3D"line-height: 100%; tex=
t-align: center; vertical-align: middle;"><img style=3D"width: 14px;
height=
: 12px; background: none no-repeat 0px 0px" border=3D"0"
src=3D"http://engi=
ne-test:8080/webadmin/webadmin/clear.cache.gif" src=3D"http://engine-test:8=
080/webadmin/webadmin/clear.cache.gif"></div></div></td><td
class=3D"GI4LN0=
DIDB GI4LN0DKDB GI4LN0DBEB"><div title=3D"" style=3D"outline:
medium none;"=
<div id=3D"gwt-uid-1182_col1_row2">2012-May-16,
16:05:03</div></div></td><=
td class=3D"GI4LN0DIDB
GI4LN0DKDB GI4LN0DFEB GI4LN0DBEB"><div title=3D"" st=
yle=3D"outline: medium none;"><div
id=3D"gwt-uid-1182_col2_row2">Host kvm04=
was autorecovered.</div></div></td></tr><tr
class=3D"GI4LN0DJEB"><td class=
=3D"GI4LN0DIDB GI4LN0DKEB GI4LN0DLDB"><div
style=3D"outline:none;"><div sty=
le=3D"line-height: 100%; text-align: center; vertical-align: middle;"><img
=
style=3D"width: 14px; height: 12px; background: none no-repeat 0px 0px" bor=
der=3D"0"
src=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.gif"=
src=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.gif"></div></=
div></td><td class=3D"GI4LN0DIDB GI4LN0DKEB"><div
title=3D"" style=3D"outli=
ne: medium none;"><div id=3D"gwt-uid-1182_col1_row3">2012-May-16,
16:05:03<=
/div></div></td><td class=3D"GI4LN0DIDB GI4LN0DKEB
GI4LN0DFEB"><div title=
=3D"" style=3D"outline: medium none;"><div
id=3D"gwt-uid-1182_col2_row3">Ho=
st kvm04 is compatible with versions (3.0,3.1) and cannot join Cluster Defa=
ult which is set to version 3.1.</div></div></td></tr><tr
class=3D"GI4LN0DJ=
DB"><td class=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DLDB"><div
style=3D"outline:no=
ne;"><div style=3D"line-height: 100%; text-align: center; vertical-align:
m=
iddle;"><img style=3D"width: 14px; height: 12px; background: none
no-repeat=
0px 0px" border=3D"0"
src=3D"http://engine-test:8080/webadmin/webadmin/cle=
ar.cache.gif" src=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.=
gif"></div></div></td><td class=3D"GI4LN0DIDB
GI4LN0DKDB"><div style=3D"out=
line:none;"><div id=3D"gwt-uid-1182_col1_row4">2012-May-16,
16:01:02</div><=
/div></td><td class=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DFEB"><div
title=3D"" st=
yle=3D"outline: medium none;"><div
id=3D"gwt-uid-1182_col2_row4">Host kvm04=
was activated by
admin@internal.</div></div></td></tr></tbody></table><br>=
if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to
Up.<br><br>=
<br><br><br><font color=3D"#666">=D0=A1=D1=80=D0=B4 16
=D0=9C=D0=B0=D0=B9 2=
012 15:24:36 +0400, Haim Ateya &lt;hateya(a)redhat.com&gt; =D0=BD=D0=B0=D0=
=BF=D0=B8=D1=81=D0=B0=D0=BB:</font><br><blockquote
style=3D"padding-left:10=
px; margin:10px 10px 10px 0px; border-left:#aaa 2px dotted"><div
style=3D"f=
ont-family: Arial; font-size: 10pt; color: #000000"><font face=3D"arial,
he=
lvetica, sans-serif" size=3D"2">I guess you compiled vdsm yourself,
please =
run the following command from your host:</font><div
style=3D"color: =
rgb(0, 0, 0); "><font face=3D"arial, helvetica, sans-serif"
size=3D"2"><br>=
</font></div><div style=3D"color: rgb(0, 0, 0); "><font
face=3D"arial, helv=
etica, sans-serif" size=3D"2">vdsClient -s 0 getVdsCaps (assuming you
work =
with SSL). </font></div><div style=3D"color: rgb(0, 0, 0);
"><font fac=
e=3D"arial, helvetica, sans-serif"
size=3D"2"><br></font></div><div><font f=
ace=3D"arial, helvetica, sans-serif" size=3D"2">anyhow,
it smells =
;like a known issue with latest build where vdsm returns supported_clusters=
=3D 3.0 and engine reject host, but lets find
out. </font></div><div>=
<font face=3D"arial, helvetica, sans-serif"
size=3D"2"><br></font></div><di=
v><font face=3D"arial, helvetica, sans-serif"
size=3D"2">Thanks, </fon=
t></div><div><font face=3D"arial, helvetica, sans-serif"
size=3D"2"><br></f=
ont></div><div><font face=3D"arial, helvetica, sans-serif"
size=3D"2">Haim<=
/font></div><div><br><hr style=3D"color: rgb(0, 0, 0);
font-family: Arial; =
font-size: 10pt; "><blockquote style=3D"border-left-width: 2px;
border-left=
-style: solid; border-left-color: rgb(16, 16, 255); margin-left: 5px; paddi=
ng-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal;=
text-decoration: none; font-family: Helvetica, Arial, sans-serif; font-siz=
e: 12pt; "><b>From: </b>ovirt(a)qip.ru<br><b>To:
</b>users(a)ovirt.org<br><b>Se=
nt: </b>Wednesday, May 16, 2012 1:58:33 PM<br><b>Subject:
</b>[Users] Host =
can't join the cluster<br><br>After upgrade of vdsm from
4.9.6-0.196.=
gitb8b79b5 to 4.9.6-0.201.git98e8078<br><br>engine set host in nonoperation=
al mode, the error is<br><br><br><div title=3D""
style=3D"outline: medium n=
one;"><div>"Host kvm04 is compatible with versions (3.0,3.1) and cannot
joi=
n Cluster Default which is set to version
3.1."</div></div><br><br>--<br><b=
r>
<br>_______________________________________________<br>Users mailing
list<b=
r>Users(a)ovirt.org<br><a style=3D"border-bottom:1px dotted;
text-decoration:=
none" target=3D"_blank"
href=3D"http://lists.ovirt.org/mailman/listinfo/us=
ers" title=3D"=D0=9E=D1=82=D0=BA=D1=80=D1=8B=D1=82=D1=8C =D0=B2=D0=BD=D0=
=B5=D1=88=D0=BD=D1=8E=D1=8E =D1=81=D1=81=D1=8B=D0=BB=D0=BA=D1=83">http://li=
sts.ovirt.org/mailman/listinfo/users</a><br></blockquote&g...
</blockquote><br><br>--<br>
<br>
</blockquote><br></div></div></body></html>
--=_ef2cb314-a01b-4313-84f2-4a7c34d7baaf--
10:46 a.m.
New subject: [Users] Host can't join the cluster
This is a message in Mime Format. If you see this, your mail reader does not support this
format.
--=_0fa9871bf7398178d37373d8455ddd63
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Yes, this work, status is now UP=0A=0A=D0=A1=D1=80=D0=B4 16 =D0=9C=D0=B0=
=D0=B9 2012 17:59:46 +0400, Haim Ateya =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=
=D0=B0=D0=BB:=0AThis issue was introduced in Ic7b4a63a974bfc301f3294603d=
8fe91f534b74dd (http://gerrit.ovirt.org/4284), we are currently working=
to resolve this issueand patch will be sent soon. meantime, you can edi=
t /usr/share/vdsm/dsaversion.py and change the following fields:software=
_version =3D "4.9"software_revision =3D "0=0Arestart vdsmd service and a=
ctivate host again. =0AHaim=0AFrom: ovirt(a)qip.ru=0ATo: "Haim Ateya" =0AC=
c: users(a)ovirt.org=0ASent: Wednesday, May 16, 2012 3:19:04 PM=0ASubject:=
Re: Re: [Users] Host can't jo=C2=ADin the cluster=0A=0A in secure and n=
on secure connections i have the same nonoperational status=0A=0Athe out=
put of getVdsCaps on host is empty=0A=0Athis is event log in webadmin=0A=
=0A2012-May-16, 16:05:04Host kvm04 is compatible with versions (3.0,3.1)=
and cannot join Cluster Default which is set to version 3.1.2012-May-16=
, 16:05:04Detected new Host kvm04. Host state was set to Up.2012-May-16,=
16:05:03Host kvm04 was autorecovered.2012-May-16, 16:05:03Host kvm04 is=
compatible with versions (3.0,3.1) and cannot join Cluster Default whic=
h is set to version 3.1.2012-May-16, 16:01:02Host kvm04 was activated by=
admin(a)internal.=0Aif i do downgrade to 4.9.6-0.196.gitb8b79b5 host stat=
e set's to Up.=0A=0A=D0=A1=D1=80=D0=B4 16 =D0=9C=D0=B0=D0=B9 2012 15:24:=
36 +0400, Haim Ateya =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:=0AI gu=
ess you compiled vdsm yourself, please run the following command from y=
our host:=0AvdsClient -s 0 getVdsCaps (assuming you work with SSL). =0Aa=
nyhow, it smells like a known issue with latest build where vdsm returns=
supported_clusters =3D 3.0 and engine reject host, but lets find out.=
=0AThanks, =0AHaim=0AFrom: ovirt(a)qip.ru=0ATo: users(a)ovirt.org=0ASent: W=
ednesday, May 16, 2012 1:58:33 PM=0ASubject: [Users] Host can't join the=
cluster=0A=0AAfter upgrade of vdsm from 4.9.6-0.196.gitb8b79b5 to 4.9.=
6-0.201.git98e8078=0A=0Aengine set host in nonoperational mode, the erro=
r is=0A=0A"Host kvm04 is compatible with versions (3.0,3.1) and cannot j=
oin Cluster Default which is set to version 3.1."=0A=0A--=0A=0A_________=
______________________________________=0AUsers mailing list=0AUsers@ovir=
t.org=0Ahttp://lists.ovirt.org/mailman/listinfo/users=0A=0A--=0A=0A--
--=_0fa9871bf7398178d37373d8455ddd63
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Yes, this work, status is now UP<br><br><br><br><br><font
color=3D"#666"=
=D0=A1=D1=80=D0=B4 16 =D0=9C=D0=B0=D0=B9 2012 17:59:46 +0400, Haim
Atey=
a &lt;hateya(a)redhat.com&gt;
=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:<=
/font><br><blockquote style=3D"padding-left:10px; margin:10px 10px 10px=
0px; border-left:#aaa 2px dotted"><div style=3D"font-family: Arial; fon=
t-size: 10pt; color: #000000"><font face=3D"Arial"
size=3D"2">This issue=
was introduced in Ic7b4a63a974bfc301f3294603d8fe91f534b74dd (<a style=
=3D"border-bottom:1px dotted; text-decoration: none" target=3D"_blank"
h=
ref=3D"http://gerrit.ovirt.org/4284" title=3D"=D0=9E=D1=82=D0=BA=D1=80=
=D1=8B=D1=82=D1=8C =D0=B2=D0=BD=D0=B5=D1=88=D0=BD=D1=8E=D1=8E =D1=81=D1=
=81=D1=8B=D0=BB=D0=BA=D1=83">http://gerrit.ovirt.org/4284</a>), we are c=
urrently working to resolve this issue</font><div style=3D"color: rgb(0,=
0, 0); font-family: Arial; font-size: 10pt; ">and patch will be sent so=
on. </div><div style=3D"color: rgb(0, 0, 0); font-family: Arial;
fo=
nt-size: 10pt; ">meantime, you can edit /usr/share/vdsm/dsaversion.py an=
d change the following fields:</div><div><div style=3D"color: rgb(0,
0,=
0); font-family: Arial; font-size: 10pt; ">software_version =3D
"4.9"</=
div><div style=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 10=
pt; ">software_revision =3D "0</div><div style=3D"color: rgb(0,
0, 0); f=
ont-family: Arial; font-size: 10pt; "><br></div><div
style=3D"color: rgb=
(0, 0, 0); font-family: Arial; font-size: 10pt; ">restart vdsmd service=
and activate host again. </div><div style=3D"color: rgb(0, 0,
0);=
font-family: Arial; font-size: 10pt; "><br></div><div
style=3D"color: r=
gb(0, 0, 0); font-family: Arial; font-size: 10pt;
">Haim</div><br><hr xs=
scleaned=3D"zwchr" style=3D"color: rgb(0, 0, 0); font-family: Arial; fon=
t-size: 10pt; "><blockquote style=3D"border-left-width: 2px; border-left=
-style: solid; border-left-color: rgb(16, 16, 255); margin-left: 5px; pa=
dding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: n=
ormal; text-decoration: none; font-family: Helvetica, Arial, sans-serif;=
font-size: 12pt; "><b>From: </b>ovirt(a)qip.ru<br><b>To:
</b>"Haim Ateya"=
&lt;hateya(a)redhat.com&gt;<br><b>Cc:
</b>users(a)ovirt.org<br><b>Sent: </b=
Wednesday, May 16, 2012 3:19:04 PM<br><b>Subject:
</b>Re: Re: [Users] H=
ost can't jo=C2=ADin the
cluster<br><br><!-- <link rel=3D"stylesheet" hr=
ef=3D"/zimbra/css/msgview.css?v=3D110804122015"> --> in secure
and=
non secure connections i have the same nonoperational status<br><br>the=
output of <font face=3D"arial, helvetica, sans-serif"
size=3D"2">getVds=
Caps on host </font>is empty <br><br><br>this is event log in
webadmin<b=
r><br><table xsscleaned=3D"GI4LN0DAFB"
cellspacing=3D"0"><tbody><tr xssc=
leaned=3D"GI4LN0DJDB"><td xsscleaned=3D"GI4LN0DIDB GI4LN0DKDB
GI4LN0DLDB=
"><div style=3D"outline:none;"><div style=3D"line-height:
100%; text-ali=
gn: center; vertical-align: middle;"><img style=3D"width: 14px; height:=
12px; background: none no-repeat 0px 0px" src=3D"http://engine-test:808=
0/webadmin/webadmin/clear.cache.gif"
border=3D"0"></div></div></td><td x=
sscleaned=3D"GI4LN0DIDB GI4LN0DKDB"><div title=3D""
style=3D"outline: me=
dium none;"><div
xsscleaned=3D"gwt-uid-1182_col1_row0">2012-May-16, 16:0=
5:04</div></div></td><td xsscleaned=3D"GI4LN0DIDB GI4LN0DKDB
GI4LN0DFEB"=
<div title=3D"" style=3D"outline: medium
none;"><div xsscleaned=3D"gwt-=
uid-1182_col2_row0">Host
kvm04 is compatible with versions (3.0,3.1) and=
cannot join Cluster Default which is set to version 3.1.</div></div></t=
d></tr><tr xsscleaned=3D"GI4LN0DJEB"><td
xsscleaned=3D"GI4LN0DIDB GI4LN0=
DKEB GI4LN0DLDB"><div style=3D"outline:none;"><div
style=3D"line-height:=
100%; text-align: center; vertical-align: middle;"><img style=3D"width:=
14px; height: 12px; background: none no-repeat 0px 0px" src=3D"http://e=
ngine-test:8080/webadmin/webadmin/clear.cache.gif"
border=3D"0"></div></=
div></td><td xsscleaned=3D"GI4LN0DIDB GI4LN0DKEB"><div
title=3D"" style=
=3D"outline: medium none;"><div
xsscleaned=3D"gwt-uid-1182_col1_row1">20=
12-May-16, 16:05:04</div></div></td><td xsscleaned=3D"GI4LN0DIDB
GI4LN0D=
KEB GI4LN0DFEB"><div title=3D"" style=3D"outline: medium
none;"><div xss=
cleaned=3D"gwt-uid-1182_col2_row1">Detected new Host kvm04. Host state w=
as set to Up.</div></div></td></tr><tr
xsscleaned=3D"GI4LN0DJDB GI4LN0DA=
EB"><td xsscleaned=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DLDB
GI4LN0DBEB"><div=
style=3D"outline:none;"><div style=3D"line-height: 100%; text-align:
ce=
nter; vertical-align: middle;"><img style=3D"width: 14px; height: 12px;=
background: none no-repeat 0px 0px" src=3D"http://engine-test:8080/weba=
dmin/webadmin/clear.cache.gif"
border=3D"0"></div></div></td><td xssclea=
ned=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DBEB"><div title=3D""
style=3D"outlin=
e: medium none;"><div
xsscleaned=3D"gwt-uid-1182_col1_row2">2012-May-16,=
16:05:03</div></div></td><td xsscleaned=3D"GI4LN0DIDB
GI4LN0DKDB GI4LN0=
DFEB GI4LN0DBEB"><div title=3D"" style=3D"outline: medium
none;"><div xs=
scleaned=3D"gwt-uid-1182_col2_row2">Host kvm04 was
autorecovered.</div><=
/div></td></tr><tr xsscleaned=3D"GI4LN0DJEB"><td
xsscleaned=3D"GI4LN0DID=
B GI4LN0DKEB GI4LN0DLDB"><div style=3D"outline:none;"><div
style=3D"line=
-height: 100%; text-align: center; vertical-align: middle;"><img style=
=3D"width: 14px; height: 12px; background: none no-repeat 0px 0px" src=
=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.gif" border=3D=
"0"></div></div></td><td xsscleaned=3D"GI4LN0DIDB
GI4LN0DKEB"><div title=
=3D"" style=3D"outline: medium none;"><div
xsscleaned=3D"gwt-uid-1182_co=
l1_row3">2012-May-16, 16:05:03</div></div></td><td
xsscleaned=3D"GI4LN0D=
IDB GI4LN0DKEB GI4LN0DFEB"><div title=3D"" style=3D"outline:
medium none=
;"><div xsscleaned=3D"gwt-uid-1182_col2_row3">Host kvm04 is
compatible w=
ith versions (3.0,3.1) and cannot join Cluster Default which is set to v=
ersion 3.1.</div></div></td></tr><tr
xsscleaned=3D"GI4LN0DJDB"><td xsscl=
eaned=3D"GI4LN0DIDB GI4LN0DKDB GI4LN0DLDB"><div
style=3D"outline:none;">=
<div style=3D"line-height: 100%; text-align: center; vertical-align: mid=
dle;"><img style=3D"width: 14px; height: 12px; background: none no-repea=
t 0px 0px" src=3D"http://engine-test:8080/webadmin/webadmin/clear.cache.=
gif" border=3D"0"></div></div></td><td
xsscleaned=3D"GI4LN0DIDB GI4LN0DK=
DB"><div style=3D"outline:none;"><div
xsscleaned=3D"gwt-uid-1182_col1_ro=
w4">2012-May-16, 16:01:02</div></div></td><td
xsscleaned=3D"GI4LN0DIDB G=
I4LN0DKDB GI4LN0DFEB"><div title=3D"" style=3D"outline: medium
none;"><d=
iv xsscleaned=3D"gwt-uid-1182_col2_row4">Host kvm04 was activated by adm=
in@internal.</div></div></td></tr></tbody></table><br>if
i do downgrade=
to 4.9.6-0.196.gitb8b79b5 host state set's to
Up.<br><br><br><br><br><f=
ont color=3D"#666">=D0=A1=D1=80=D0=B4 16 =D0=9C=D0=B0=D0=B9 2012 15:24:3=
6 +0400, Haim Ateya &lt;hateya(a)redhat.com&gt; =D0=BD=D0=B0=D0=BF=D0=B8=
=D1=81=D0=B0=D0=BB:</font><br><blockquote style=3D"padding-left:10px;
ma=
rgin:10px 10px 10px 0px; border-left:#aaa 2px dotted"><div style=3D"font=
-family: Arial; font-size: 10pt; color: #000000"><font face=3D"arial, he=
lvetica, sans-serif" size=3D"2">I guess you compiled vdsm yourself,
plea=
se run the following command from your host:</font><div
style=3D"c=
olor: rgb(0, 0, 0); "><font face=3D"arial, helvetica, sans-serif"
size=
=3D"2"><br></font></div><div style=3D"color: rgb(0,
0, 0); "><font face=
=3D"arial, helvetica, sans-serif" size=3D"2">vdsClient -s 0
getVdsCaps (=
assuming you work with SSL). </font></div><div
style=3D"color: rgb(=
0, 0, 0); "><font face=3D"arial, helvetica, sans-serif"
size=3D"2"><br><=
/font></div><div><font face=3D"arial, helvetica, sans-serif"
size=3D"2">=
anyhow, it smells like a known issue with latest build where v=
dsm returns supported_clusters =3D 3.0 and engine reject host, but lets=
find out. </font></div><div><font face=3D"arial,
helvetica, sans-s=
erif" size=3D"2"><br></font></div><div><font
face=3D"arial, helvetica, s=
ans-serif"
size=3D"2">Thanks, </font></div><div><font
face=3D"arial=
, helvetica, sans-serif"
size=3D"2"><br></font></div><div><font
face=3D"=
arial, helvetica, sans-serif"
size=3D"2">Haim</font></div><div><br><hr s=
tyle=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 10pt; "><blo=
ckquote style=3D"border-left-width: 2px; border-left-style: solid; borde=
r-left-color: rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; col=
or: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decorati=
on: none; font-family: Helvetica, Arial, sans-serif; font-size: 12pt; ">=
<b>From: </b>ovirt(a)qip.ru<br><b>To:
</b>users(a)ovirt.org<br><b>Sent: </b>=
Wednesday, May 16, 2012 1:58:33 PM<br><b>Subject: </b>[Users] Host
can't=
join the cluster<br><br>After upgrade of vdsm from 4.9.6-0.196.gi=
tb8b79b5 to 4.9.6-0.201.git98e8078<br><br>engine set host in nonoperatio=
nal mode, the error is<br><br><br><div title=3D""
style=3D"outline: medi=
um none;"><div>"Host kvm04 is compatible with versions (3.0,3.1) and
can=
not join Cluster Default which is set to version
3.1."</div></div><br><b=
r>--<br><br>=0D=0A<br>_______________________________________________<br=
Users mailing list<br>Users(a)ovirt.org<br><a
style=3D"border-bottom:1px=
dotted; text-decoration: none"
target=3D"_blank" href=3D"http://lists.o=
virt.org/mailman/listinfo/users" title=3D"=D0=9E=D1=82=D0=BA=D1=80=D1=8B=
=D1=82=D1=8C =D0=B2=D0=BD=D0=B5=D1=88=D0=BD=D1=8E=D1=8E =D1=81=D1=81=D1=
=8B=D0=BB=D0=BA=D1=83">http://lists.ovirt.org/mailman/listinfo/users</a>=
<br></blockquote><br></div></div>=0D=0A</blockquote><br><br>--<br>=0D=0A=
<br>=0D=0A</blockquote><br></div></div>=0D=0A</blockquote><br><br>--<br>=
=0D=0A<br>
--=_0fa9871bf7398178d37373d8455ddd63--
10:51 a.m.
New subject: [Users] Host can't join the cluster
How difficult would it be for Engine to handle the true
version-release of vdsm?
As a stop-gap measure, Engine could convert the reported version-release
into the floating point numbers it can handle. The same stop-gap could
be done on Vdsm side, but I consider this as a step backward.
On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
This issue was introduced in
Ic7b4a63a974bfc301f3294603d8fe91f534b74dd (http://gerrit.ovirt.org/4284), we are currently
working to resolve this issue
and patch will be sent soon.
meantime, you can edit /usr/share/vdsm/dsaversion.py and change the following fields:
software_version = "4.9"
software_revision = "0
restart vdsmd service and activate host again.
Haim
----- Original Message -----
> From: ovirt(a)qip.ru
> To: "Haim Ateya" <hateya(a)redhat.com>
> Cc: users(a)ovirt.org
> Sent: Wednesday, May 16, 2012 3:19:04 PM
> Subject: Re: Re: [Users] Host can't join the cluster
> in secure and non secure connections i have the same nonoperational
> status
> the output of getVdsCaps on host is empty
> this is event log in webadmin
>
> 2012-May-16, 16:05:04
> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
> Cluster Default which is set to version 3.1.
>
> 2012-May-16, 16:05:04
> Detected new Host kvm04. Host state was set to Up.
>
> 2012-May-16, 16:05:03
> Host kvm04 was autorecovered.
>
> 2012-May-16, 16:05:03
> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
> Cluster Default which is set to version 3.1.
>
> 2012-May-16, 16:01:02
> Host kvm04 was activated by admin@internal.
> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to Up.
> Срд 16 Май 2012 15:24:36 +0400, Haim Ateya <hateya(a)redhat.com>
> написал:
> > I guess you compiled vdsm yourself, please run the following
> > command
> > from your host:
>
> > vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>
> > anyhow, it smells like a known issue with latest build where vdsm
> > returns supported_clusters = 3.0 and engine reject host, but lets
> > find out.
1:50 p.m.
New subject: [Users] Host can't join the cluster
On 05/16/2012 05:51 PM, Dan Kenigsberg wrote:
How difficult would it be for Engine to handle the true
version-release of vdsm?
As a stop-gap measure, Engine could convert the reported version-release
into the floating point numbers it can handle. The same stop-gap could
be done on Vdsm side, but I consider this as a step backward.
why does engine cares about vdsm version, rather than compatibility
levels reported by vdsm?
On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
> This issue was introduced in Ic7b4a63a974bfc301f3294603d8fe91f534b74dd
(http://gerrit.ovirt.org/4284), we are currently working to resolve this issue
> and patch will be sent soon.
> meantime, you can edit /usr/share/vdsm/dsaversion.py and change the following
fields:
>
> software_version = "4.9"
> software_revision = "0
>
> restart vdsmd service and activate host again.
>
> Haim
> ----- Original Message -----
>
>> From: ovirt(a)qip.ru
>> To: "Haim Ateya"<hateya(a)redhat.com>
>> Cc: users(a)ovirt.org
>> Sent: Wednesday, May 16, 2012 3:19:04 PM
>> Subject: Re: Re: [Users] Host can't join the cluster
>
>> in secure and non secure connections i have the same nonoperational
>> status
>
>> the output of getVdsCaps on host is empty
>
>> this is event log in webadmin
>
>>
>
>> 2012-May-16, 16:05:04
>
>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>> Cluster Default which is set to version 3.1.
>
>>
>
>> 2012-May-16, 16:05:04
>
>> Detected new Host kvm04. Host state was set to Up.
>
>>
>
>> 2012-May-16, 16:05:03
>
>> Host kvm04 was autorecovered.
>
>>
>
>> 2012-May-16, 16:05:03
>
>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>> Cluster Default which is set to version 3.1.
>
>>
>
>> 2012-May-16, 16:01:02
>
>> Host kvm04 was activated by admin@internal.
>> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to Up.
>
>> Срд 16 Май 2012 15:24:36 +0400, Haim Ateya<hateya(a)redhat.com>
>> написал:
>
>>> I guess you compiled vdsm yourself, please run the following
>>> command
>>> from your host:
>>
>
>>> vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>>
>
>>> anyhow, it smells like a known issue with latest build where vdsm
>>> returns supported_clusters = 3.0 and engine reject host, but lets
>>> find out.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:28 a.m.
New subject: [Users] Host can't join the cluster
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Dan Kenigsberg" <danken(a)redhat.com>
Cc: "Haim Ateya" <hateya(a)redhat.com>, users(a)ovirt.org, "Omer
Frenkel" <ofrenkel(a)redhat.com>
Sent: Wednesday, May 16, 2012 8:50:59 PM
Subject: Re: [Users] Host can't join the cluster
On 05/16/2012 05:51 PM, Dan Kenigsberg wrote:
> How difficult would it be for Engine to handle the true
> version-release of vdsm?
>
> As a stop-gap measure, Engine could convert the reported
> version-release
> into the floating point numbers it can handle. The same stop-gap
> could
> be done on Vdsm side, but I consider this as a step backward.
why does engine cares about vdsm version, rather than compatibility
levels reported by vdsm?
the definition was, as i remember:
vdsm reports which engine (cluster levels) it supports.
engine reports which vdsm versions it supports.
both must apply so a host would be active.
>
> On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
>> This issue was introduced in
>> Ic7b4a63a974bfc301f3294603d8fe91f534b74dd
>> (http://gerrit.ovirt.org/4284), we are currently working to
>> resolve this issue
>> and patch will be sent soon.
>> meantime, you can edit /usr/share/vdsm/dsaversion.py and change
>> the following fields:
>>
>> software_version = "4.9"
>> software_revision = "0
>>
>> restart vdsmd service and activate host again.
>>
>> Haim
>> ----- Original Message -----
>>
>>> From: ovirt(a)qip.ru
>>> To: "Haim Ateya"<hateya(a)redhat.com>
>>> Cc: users(a)ovirt.org
>>> Sent: Wednesday, May 16, 2012 3:19:04 PM
>>> Subject: Re: Re: [Users] Host can't join the cluster
>>
>>> in secure and non secure connections i have the same
>>> nonoperational
>>> status
>>
>>> the output of getVdsCaps on host is empty
>>
>>> this is event log in webadmin
>>
>>>
>>
>>> 2012-May-16, 16:05:04
>>
>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>>> Cluster Default which is set to version 3.1.
>>
>>>
>>
>>> 2012-May-16, 16:05:04
>>
>>> Detected new Host kvm04. Host state was set to Up.
>>
>>>
>>
>>> 2012-May-16, 16:05:03
>>
>>> Host kvm04 was autorecovered.
>>
>>>
>>
>>> 2012-May-16, 16:05:03
>>
>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>>> Cluster Default which is set to version 3.1.
>>
>>>
>>
>>> 2012-May-16, 16:01:02
>>
>>> Host kvm04 was activated by admin@internal.
>>> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to
>>> Up.
>>
>>> Срд 16 Май 2012 15:24:36 +0400, Haim Ateya<hateya(a)redhat.com>
>>> написал:
>>
>>>> I guess you compiled vdsm yourself, please run the following
>>>> command
>>>> from your host:
>>>
>>
>>>> vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>>>
>>
>>>> anyhow, it smells like a known issue with latest build where
>>>> vdsm
>>>> returns supported_clusters = 3.0 and engine reject host, but
>>>> lets
>>>> find out.
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
4:30 a.m.
New subject: [Users] Host can't join the cluster
On 05/17/2012 11:28 AM, Omer Frenkel wrote:
----- Original Message -----
> From: "Itamar Heim"<iheim(a)redhat.com>
> To: "Dan Kenigsberg"<danken(a)redhat.com>
> Cc: "Haim Ateya"<hateya(a)redhat.com>, users(a)ovirt.org, "Omer
Frenkel"<ofrenkel(a)redhat.com>
> Sent: Wednesday, May 16, 2012 8:50:59 PM
> Subject: Re: [Users] Host can't join the cluster
>
> On 05/16/2012 05:51 PM, Dan Kenigsberg wrote:
>> How difficult would it be for Engine to handle the true
>> version-release of vdsm?
>>
>> As a stop-gap measure, Engine could convert the reported
>> version-release
>> into the floating point numbers it can handle. The same stop-gap
>> could
>> be done on Vdsm side, but I consider this as a step backward.
>
> why does engine cares about vdsm version, rather than compatibility
> levels reported by vdsm?
>
the definition was, as i remember:
vdsm reports which engine (cluster levels) it supports.
engine reports which vdsm versions it supports.
both must apply so a host would be active.
well, first, then the error message is wrong and misleading (complains a
vdsm with compat levels of (3.0,3.1) can't join the cluster which is 3.1).
second, iirc, the definition was vdsm can override engine vdsm version
check, so a newer vdsm could still report it will work with an older
engine, without needing to change the older engine to match it?
>>
>> On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
>>> This issue was introduced in
>>> Ic7b4a63a974bfc301f3294603d8fe91f534b74dd
>>> (http://gerrit.ovirt.org/4284), we are currently working to
>>> resolve this issue
>>> and patch will be sent soon.
>>> meantime, you can edit /usr/share/vdsm/dsaversion.py and change
>>> the following fields:
>>>
>>> software_version = "4.9"
>>> software_revision = "0
>>>
>>> restart vdsmd service and activate host again.
>>>
>>> Haim
>>> ----- Original Message -----
>>>
>>>> From: ovirt(a)qip.ru
>>>> To: "Haim Ateya"<hateya(a)redhat.com>
>>>> Cc: users(a)ovirt.org
>>>> Sent: Wednesday, May 16, 2012 3:19:04 PM
>>>> Subject: Re: Re: [Users] Host can't join the cluster
>>>
>>>> in secure and non secure connections i have the same
>>>> nonoperational
>>>> status
>>>
>>>> the output of getVdsCaps on host is empty
>>>
>>>> this is event log in webadmin
>>>
>>>>
>>>
>>>> 2012-May-16, 16:05:04
>>>
>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>>>> Cluster Default which is set to version 3.1.
>>>
>>>>
>>>
>>>> 2012-May-16, 16:05:04
>>>
>>>> Detected new Host kvm04. Host state was set to Up.
>>>
>>>>
>>>
>>>> 2012-May-16, 16:05:03
>>>
>>>> Host kvm04 was autorecovered.
>>>
>>>>
>>>
>>>> 2012-May-16, 16:05:03
>>>
>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>>>> Cluster Default which is set to version 3.1.
>>>
>>>>
>>>
>>>> 2012-May-16, 16:01:02
>>>
>>>> Host kvm04 was activated by admin@internal.
>>>> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to
>>>> Up.
>>>
>>>> Срд 16 Май 2012 15:24:36 +0400, Haim Ateya<hateya(a)redhat.com>
>>>> написал:
>>>
>>>>> I guess you compiled vdsm yourself, please run the following
>>>>> command
>>>>> from your host:
>>>>
>>>
>>>>> vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>>>>
>>>
>>>>> anyhow, it smells like a known issue with latest build where
>>>>> vdsm
>>>>> returns supported_clusters = 3.0 and engine reject host, but
>>>>> lets
>>>>> find out.
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
7:11 a.m.
New subject: [Users] Host can't join the cluster
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Omer Frenkel" <ofrenkel(a)redhat.com>
Cc: "Haim Ateya" <hateya(a)redhat.com>, users(a)ovirt.org, "Dan
Kenigsberg" <danken(a)redhat.com>
Sent: Thursday, May 17, 2012 11:30:34 AM
Subject: Re: [Users] Host can't join the cluster
On 05/17/2012 11:28 AM, Omer Frenkel wrote:
>
>
> ----- Original Message -----
>> From: "Itamar Heim"<iheim(a)redhat.com>
>> To: "Dan Kenigsberg"<danken(a)redhat.com>
>> Cc: "Haim Ateya"<hateya(a)redhat.com>, users(a)ovirt.org,
"Omer
>> Frenkel"<ofrenkel(a)redhat.com>
>> Sent: Wednesday, May 16, 2012 8:50:59 PM
>> Subject: Re: [Users] Host can't join the cluster
>>
>> On 05/16/2012 05:51 PM, Dan Kenigsberg wrote:
>>> How difficult would it be for Engine to handle the true
>>> version-release of vdsm?
>>>
>>> As a stop-gap measure, Engine could convert the reported
>>> version-release
>>> into the floating point numbers it can handle. The same stop-gap
>>> could
>>> be done on Vdsm side, but I consider this as a step backward.
>>
>> why does engine cares about vdsm version, rather than
>> compatibility
>> levels reported by vdsm?
>>
>
> the definition was, as i remember:
> vdsm reports which engine (cluster levels) it supports.
> engine reports which vdsm versions it supports.
> both must apply so a host would be active.
well, first, then the error message is wrong and misleading
(complains a
vdsm with compat levels of (3.0,3.1) can't join the cluster which is
3.1).
i agree
second, iirc, the definition was vdsm can override engine vdsm
version
check, so a newer vdsm could still report it will work with an older
engine, without needing to change the older engine to match it?
i agree as well, i think the intention was for newer builds in the same version,
so revision can be changed, but major version should be coordinated with the engine.
maybe the logic can changed just to make sure
there is a match between supported cluster levels in vdsm and engine
and ignore engine / vdsm software versions
>
>>>
>>> On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
>>>> This issue was introduced in
>>>> Ic7b4a63a974bfc301f3294603d8fe91f534b74dd
>>>> (http://gerrit.ovirt.org/4284), we are currently working to
>>>> resolve this issue
>>>> and patch will be sent soon.
>>>> meantime, you can edit /usr/share/vdsm/dsaversion.py and change
>>>> the following fields:
>>>>
>>>> software_version = "4.9"
>>>> software_revision = "0
>>>>
>>>> restart vdsmd service and activate host again.
>>>>
>>>> Haim
>>>> ----- Original Message -----
>>>>
>>>>> From: ovirt(a)qip.ru
>>>>> To: "Haim Ateya"<hateya(a)redhat.com>
>>>>> Cc: users(a)ovirt.org
>>>>> Sent: Wednesday, May 16, 2012 3:19:04 PM
>>>>> Subject: Re: Re: [Users] Host can't join the cluster
>>>>
>>>>> in secure and non secure connections i have the same
>>>>> nonoperational
>>>>> status
>>>>
>>>>> the output of getVdsCaps on host is empty
>>>>
>>>>> this is event log in webadmin
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:04
>>>>
>>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot
>>>>> join
>>>>> Cluster Default which is set to version 3.1.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:04
>>>>
>>>>> Detected new Host kvm04. Host state was set to Up.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:03
>>>>
>>>>> Host kvm04 was autorecovered.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:03
>>>>
>>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot
>>>>> join
>>>>> Cluster Default which is set to version 3.1.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:01:02
>>>>
>>>>> Host kvm04 was activated by admin@internal.
>>>>> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to
>>>>> Up.
>>>>
>>>>> Срд 16 Май 2012 15:24:36 +0400, Haim Ateya<hateya(a)redhat.com>
>>>>> написал:
>>>>
>>>>>> I guess you compiled vdsm yourself, please run the following
>>>>>> command
>>>>>> from your host:
>>>>>
>>>>
>>>>>> vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>>>>>
>>>>
>>>>>> anyhow, it smells like a known issue with latest build where
>>>>>> vdsm
>>>>>> returns supported_clusters = 3.0 and engine reject host, but
>>>>>> lets
>>>>>> find out.
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
3:03 p.m.
New subject: [Users] Host can't join the cluster
On 05/17/2012 02:11 PM, Omer Frenkel wrote:
...
>
> second, iirc, the definition was vdsm can override engine vdsm
> version
> check, so a newer vdsm could still report it will work with an older
> engine, without needing to change the older engine to match it?
>
i agree as well, i think the intention was for newer builds in the same version,
so revision can be changed, but major version should be coordinated with the engine.
maybe the logic can changed just to make sure
there is a match between supported cluster levels in vdsm and engine
and ignore engine / vdsm software versions
indeed.
and code seems to be correct for that flow.
either engine has support for vdsm version.
or
vdsm reports it supports this engine version.
so danken - i think the missing part is actually vdsm telling engine 3.1
version is supported:
in
./vdsm/dsaversion.py.in: 'supportedRHEVMs': ['3.0'],
(and yes, need to change this to supportedEngine naming, but i suggest
doing this in a separate patch for engine to do this with backward
compatibility)
>>
>>>>
>>>> On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
>>>>> This issue was introduced in
>>>>> Ic7b4a63a974bfc301f3294603d8fe91f534b74dd
>>>>> (http://gerrit.ovirt.org/4284), we are currently working to
>>>>> resolve this issue
>>>>> and patch will be sent soon.
>>>>> meantime, you can edit /usr/share/vdsm/dsaversion.py and change
>>>>> the following fields:
>>>>>
>>>>> software_version = "4.9"
>>>>> software_revision = "0
>>>>>
>>>>> restart vdsmd service and activate host again.
>>>>>
>>>>> Haim
>>>>> ----- Original Message -----
>>>>>
>>>>>> From: ovirt(a)qip.ru
>>>>>> To: "Haim Ateya"<hateya(a)redhat.com>
>>>>>> Cc: users(a)ovirt.org
>>>>>> Sent: Wednesday, May 16, 2012 3:19:04 PM
>>>>>> Subject: Re: Re: [Users] Host can't join the cluster
>>>>>
>>>>>> in secure and non secure connections i have the same
>>>>>> nonoperational
>>>>>> status
>>>>>
>>>>>> the output of getVdsCaps on host is empty
>>>>>
>>>>>> this is event log in webadmin
>>>>>
>>>>>>
>>>>>
>>>>>> 2012-May-16, 16:05:04
>>>>>
>>>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot
>>>>>> join
>>>>>> Cluster Default which is set to version 3.1.
>>>>>
>>>>>>
>>>>>
>>>>>> 2012-May-16, 16:05:04
>>>>>
>>>>>> Detected new Host kvm04. Host state was set to Up.
>>>>>
>>>>>>
>>>>>
>>>>>> 2012-May-16, 16:05:03
>>>>>
>>>>>> Host kvm04 was autorecovered.
>>>>>
>>>>>>
>>>>>
>>>>>> 2012-May-16, 16:05:03
>>>>>
>>>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot
>>>>>> join
>>>>>> Cluster Default which is set to version 3.1.
>>>>>
>>>>>>
>>>>>
>>>>>> 2012-May-16, 16:01:02
>>>>>
>>>>>> Host kvm04 was activated by admin@internal.
>>>>>> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's
to
>>>>>> Up.
>>>>>
>>>>>> Срд 16 Май 2012 15:24:36 +0400, Haim
Ateya<hateya(a)redhat.com>
>>>>>> написал:
>>>>>
>>>>>>> I guess you compiled vdsm yourself, please run the following
>>>>>>> command
>>>>>>> from your host:
>>>>>>
>>>>>
>>>>>>> vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>>>>>>
>>>>>
>>>>>>> anyhow, it smells like a known issue with latest build where
>>>>>>> vdsm
>>>>>>> returns supported_clusters = 3.0 and engine reject host, but
>>>>>>> lets
>>>>>>> find out.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>
>
9:20 a.m.
New subject: [Users] Host can't join the cluster
On Thu, May 17, 2012 at 10:03:31PM +0300, Itamar Heim wrote:
On 05/17/2012 02:11 PM, Omer Frenkel wrote:
...
>>
>>second, iirc, the definition was vdsm can override engine vdsm
>>version
>>check, so a newer vdsm could still report it will work with an older
>>engine, without needing to change the older engine to match it?
>>
>
>i agree as well, i think the intention was for newer builds in the same version,
>so revision can be changed, but major version should be coordinated with the engine.
>maybe the logic can changed just to make sure
>there is a match between supported cluster levels in vdsm and engine
>and ignore engine / vdsm software versions
indeed.
and code seems to be correct for that flow.
either engine has support for vdsm version.
or
vdsm reports it supports this engine version.
so danken - i think the missing part is actually vdsm telling engine
3.1 version is supported:
in
./vdsm/dsaversion.py.in: 'supportedRHEVMs': ['3.0'],
(and yes, need to change this to supportedEngine naming, but i
suggest doing this in a separate patch for engine to do this with
backward compatibility)
I do not mind adding 3.1 to supportedRHEVMs on vdsm side, but I think
that if vdsm reports that it supports clusterLevel 3.1, Engine should
believe vdsm. supportedRHEVMs was intended as a hack to allow new vdsms
tell old Engines that they are fine. That should not be the main path of
fixing the issue.
Dan.
10:54 a.m.
New subject: [Users] Host can't join the cluster
On 05/18/2012 04:20 PM, Dan Kenigsberg wrote:
On Thu, May 17, 2012 at 10:03:31PM +0300, Itamar Heim wrote:
> On 05/17/2012 02:11 PM, Omer Frenkel wrote:
> ...
>
>>>
>>> second, iirc, the definition was vdsm can override engine vdsm
>>> version
>>> check, so a newer vdsm could still report it will work with an older
>>> engine, without needing to change the older engine to match it?
>>>
>>
>> i agree as well, i think the intention was for newer builds in the same version,
>> so revision can be changed, but major version should be coordinated with the
engine.
>> maybe the logic can changed just to make sure
>> there is a match between supported cluster levels in vdsm and engine
>> and ignore engine / vdsm software versions
>
> indeed.
> and code seems to be correct for that flow.
> either engine has support for vdsm version.
> or
> vdsm reports it supports this engine version.
>
> so danken - i think the missing part is actually vdsm telling engine
> 3.1 version is supported:
> in
> ./vdsm/dsaversion.py.in: 'supportedRHEVMs': ['3.0'],
>
> (and yes, need to change this to supportedEngine naming, but i
> suggest doing this in a separate patch for engine to do this with
> backward compatibility)
I do not mind adding 3.1 to supportedRHEVMs on vdsm side, but I think
that if vdsm reports that it supports clusterLevel 3.1, Engine should
believe vdsm. supportedRHEVMs was intended as a hack to allow new vdsms
tell old Engines that they are fine. That should not be the main path of
fixing the issue.
I think there was some concept of distinguishing between supported
compatibility levels vs. supported versions of engine with that
compatibility level if engine did not specify it supports that vdsm
version (i.e., tested and supported vs. we just think this should work)
9:46 a.m.
New subject: [Users] Host can't join the cluster
On 05/19/2012 05:54 PM, Itamar Heim wrote:
On 05/18/2012 04:20 PM, Dan Kenigsberg wrote:
> On Thu, May 17, 2012 at 10:03:31PM +0300, Itamar Heim wrote:
>> On 05/17/2012 02:11 PM, Omer Frenkel wrote:
>> ...
>>
>>>>
>>>> second, iirc, the definition was vdsm can override engine vdsm
>>>> version
>>>> check, so a newer vdsm could still report it will work with an older
>>>> engine, without needing to change the older engine to match it?
>>>>
>>>
>>> i agree as well, i think the intention was for newer builds in the
>>> same version,
>>> so revision can be changed, but major version should be coordinated
>>> with the engine.
>>> maybe the logic can changed just to make sure
>>> there is a match between supported cluster levels in vdsm and engine
>>> and ignore engine / vdsm software versions
>>
>> indeed.
>> and code seems to be correct for that flow.
>> either engine has support for vdsm version.
>> or
>> vdsm reports it supports this engine version.
>>
>> so danken - i think the missing part is actually vdsm telling engine
>> 3.1 version is supported:
>> in
>> ./vdsm/dsaversion.py.in: 'supportedRHEVMs': ['3.0'],
>>
>> (and yes, need to change this to supportedEngine naming, but i
>> suggest doing this in a separate patch for engine to do this with
>> backward compatibility)
>
> I do not mind adding 3.1 to supportedRHEVMs on vdsm side, but I think
> that if vdsm reports that it supports clusterLevel 3.1, Engine should
> believe vdsm. supportedRHEVMs was intended as a hack to allow new vdsms
> tell old Engines that they are fine. That should not be the main path of
> fixing the issue.
I think there was some concept of distinguishing between supported
compatibility levels vs. supported versions of engine with that
compatibility level if engine did not specify it supports that vdsm
version (i.e., tested and supported vs. we just think this should work)
Itamar -
this is true.
The misleading error occurs as at engine code we use the same message
for both cases.
We can separate to having two error messages:
a. Incompatible cluster level
b. VDSM version not supported.
However, if we use this, it means that after every release of VDSM, we
should update the SupportedVDSMVersions (i.e - add 4.9.6 to it)
Is this what we want to do?
The other option -as previously mentioned is to rely only on cluster
compatibility level comparison (using the 'supprtedRHEVMs' reported by
VDSM)
Thoughts about this are more than welcome
Yair
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:55 a.m.
New subject: [Users] Host can't join the cluster
----- Original Message -----
From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
To: "Itamar Heim" <iheim(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Monday, May 21, 2012 4:46:20 PM
Subject: Re: [Users] Host can't join the cluster
On 05/19/2012 05:54 PM, Itamar Heim wrote:
> On 05/18/2012 04:20 PM, Dan Kenigsberg wrote:
>> On Thu, May 17, 2012 at 10:03:31PM +0300, Itamar Heim wrote:
>>> On 05/17/2012 02:11 PM, Omer Frenkel wrote:
>>> ...
>>>
>>>>>
>>>>> second, iirc, the definition was vdsm can override engine vdsm
>>>>> version
>>>>> check, so a newer vdsm could still report it will work with an
>>>>> older
>>>>> engine, without needing to change the older engine to match it?
>>>>>
>>>>
>>>> i agree as well, i think the intention was for newer builds in
>>>> the
>>>> same version,
>>>> so revision can be changed, but major version should be
>>>> coordinated
>>>> with the engine.
>>>> maybe the logic can changed just to make sure
>>>> there is a match between supported cluster levels in vdsm and
>>>> engine
>>>> and ignore engine / vdsm software versions
>>>
>>> indeed.
>>> and code seems to be correct for that flow.
>>> either engine has support for vdsm version.
>>> or
>>> vdsm reports it supports this engine version.
>>>
>>> so danken - i think the missing part is actually vdsm telling
>>> engine
>>> 3.1 version is supported:
>>> in
>>> ./vdsm/dsaversion.py.in: 'supportedRHEVMs': ['3.0'],
>>>
>>> (and yes, need to change this to supportedEngine naming, but i
>>> suggest doing this in a separate patch for engine to do this with
>>> backward compatibility)
>>
>> I do not mind adding 3.1 to supportedRHEVMs on vdsm side, but I
>> think
>> that if vdsm reports that it supports clusterLevel 3.1, Engine
>> should
>> believe vdsm. supportedRHEVMs was intended as a hack to allow new
>> vdsms
>> tell old Engines that they are fine. That should not be the main
>> path of
>> fixing the issue.
>
> I think there was some concept of distinguishing between supported
> compatibility levels vs. supported versions of engine with that
> compatibility level if engine did not specify it supports that vdsm
> version (i.e., tested and supported vs. we just think this should
> work)
Itamar - this is true.
The misleading error occurs as at engine code we use the same message
for both cases.
We can separate to having two error messages:
a. Incompatible cluster level
b. VDSM version not supported.
However, if we use this, it means that after every release of VDSM,
we
should update the SupportedVDSMVersions (i.e - add 4.9.6 to it)
Is this what we want to do?
The other option -as previously mentioned is to rely only on cluster
compatibility level comparison (using the 'supprtedRHEVMs' reported
by
VDSM)
Thoughts about this are more than welcome
Yair
i agree with this approach,
just one fix, we should use vdsm's 'supportedProtocols'
which match the engine's cluster levels.
this way the versions of the software are not important,
only what 'protocols' (or cluster levels) are supported in both.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:03 a.m.
New subject: [Users] Host can't join the cluster
On 05/21/2012 04:55 PM, Omer Frenkel wrote:
----- Original Message -----
> From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
> To: "Itamar Heim" <iheim(a)redhat.com>
> Cc: users(a)ovirt.org
> Sent: Monday, May 21, 2012 4:46:20 PM
> Subject: Re: [Users] Host can't join the cluster
>
> On 05/19/2012 05:54 PM, Itamar Heim wrote:
>> On 05/18/2012 04:20 PM, Dan Kenigsberg wrote:
>>> On Thu, May 17, 2012 at 10:03:31PM +0300, Itamar Heim wrote:
>>>> On 05/17/2012 02:11 PM, Omer Frenkel wrote:
>>>> ...
>>>>
>>>>>>
>>>>>> second, iirc, the definition was vdsm can override engine vdsm
>>>>>> version
>>>>>> check, so a newer vdsm could still report it will work with an
>>>>>> older
>>>>>> engine, without needing to change the older engine to match it?
>>>>>>
>>>>>
>>>>> i agree as well, i think the intention was for newer builds in
>>>>> the
>>>>> same version,
>>>>> so revision can be changed, but major version should be
>>>>> coordinated
>>>>> with the engine.
>>>>> maybe the logic can changed just to make sure
>>>>> there is a match between supported cluster levels in vdsm and
>>>>> engine
>>>>> and ignore engine / vdsm software versions
>>>>
>>>> indeed.
>>>> and code seems to be correct for that flow.
>>>> either engine has support for vdsm version.
>>>> or
>>>> vdsm reports it supports this engine version.
>>>>
>>>> so danken - i think the missing part is actually vdsm telling
>>>> engine
>>>> 3.1 version is supported:
>>>> in
>>>> ./vdsm/dsaversion.py.in: 'supportedRHEVMs': ['3.0'],
>>>>
>>>> (and yes, need to change this to supportedEngine naming, but i
>>>> suggest doing this in a separate patch for engine to do this with
>>>> backward compatibility)
>>>
>>> I do not mind adding 3.1 to supportedRHEVMs on vdsm side, but I
>>> think
>>> that if vdsm reports that it supports clusterLevel 3.1, Engine
>>> should
>>> believe vdsm. supportedRHEVMs was intended as a hack to allow new
>>> vdsms
>>> tell old Engines that they are fine. That should not be the main
>>> path of
>>> fixing the issue.
>>
>> I think there was some concept of distinguishing between supported
>> compatibility levels vs. supported versions of engine with that
>> compatibility level if engine did not specify it supports that vdsm
>> version (i.e., tested and supported vs. we just think this should
>> work)
> Itamar - this is true.
> The misleading error occurs as at engine code we use the same message
> for both cases.
> We can separate to having two error messages:
> a. Incompatible cluster level
> b. VDSM version not supported.
>
> However, if we use this, it means that after every release of VDSM,
> we
> should update the SupportedVDSMVersions (i.e - add 4.9.6 to it)
> Is this what we want to do?
> The other option -as previously mentioned is to rely only on cluster
> compatibility level comparison (using the 'supprtedRHEVMs' reported
> by
> VDSM)
> Thoughts about this are more than welcome
>
> Yair
i agree with this approach,
just one fix, we should use vdsm's 'supportedProtocols'
which match the engine's cluster levels.
this way the versions of the software are not important,
only what 'protocols' (or cluster levels) are supported in both.
Exactly, my bad.
Thanks for the correction!
>
>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
6:17 p.m.
New subject: [Users] Host can't join the cluster
On Mon, May 21, 2012 at 09:55:11AM -0400, Omer Frenkel wrote:
----- Original Message -----
> From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
> To: "Itamar Heim" <iheim(a)redhat.com>
> Cc: users(a)ovirt.org
> Sent: Monday, May 21, 2012 4:46:20 PM
> Subject: Re: [Users] Host can't join the cluster
>
> On 05/19/2012 05:54 PM, Itamar Heim wrote:
> > On 05/18/2012 04:20 PM, Dan Kenigsberg wrote:
> >> On Thu, May 17, 2012 at 10:03:31PM +0300, Itamar Heim wrote:
> >>> On 05/17/2012 02:11 PM, Omer Frenkel wrote:
> >>> ...
> >>>
> >>>>>
> >>>>> second, iirc, the definition was vdsm can override engine vdsm
> >>>>> version
> >>>>> check, so a newer vdsm could still report it will work with an
> >>>>> older
> >>>>> engine, without needing to change the older engine to match
it?
> >>>>>
> >>>>
> >>>> i agree as well, i think the intention was for newer builds in
> >>>> the
> >>>> same version,
> >>>> so revision can be changed, but major version should be
> >>>> coordinated
> >>>> with the engine.
> >>>> maybe the logic can changed just to make sure
> >>>> there is a match between supported cluster levels in vdsm and
> >>>> engine
> >>>> and ignore engine / vdsm software versions
> >>>
> >>> indeed.
> >>> and code seems to be correct for that flow.
> >>> either engine has support for vdsm version.
> >>> or
> >>> vdsm reports it supports this engine version.
> >>>
> >>> so danken - i think the missing part is actually vdsm telling
> >>> engine
> >>> 3.1 version is supported:
> >>> in
> >>> ./vdsm/dsaversion.py.in: 'supportedRHEVMs':
['3.0'],
> >>>
> >>> (and yes, need to change this to supportedEngine naming, but i
> >>> suggest doing this in a separate patch for engine to do this with
> >>> backward compatibility)
> >>
> >> I do not mind adding 3.1 to supportedRHEVMs on vdsm side, but I
> >> think
> >> that if vdsm reports that it supports clusterLevel 3.1, Engine
> >> should
> >> believe vdsm. supportedRHEVMs was intended as a hack to allow new
> >> vdsms
> >> tell old Engines that they are fine. That should not be the main
> >> path of
> >> fixing the issue.
> >
> > I think there was some concept of distinguishing between supported
> > compatibility levels vs. supported versions of engine with that
> > compatibility level if engine did not specify it supports that vdsm
> > version (i.e., tested and supported vs. we just think this should
> > work)
> Itamar - this is true.
> The misleading error occurs as at engine code we use the same message
> for both cases.
> We can separate to having two error messages:
> a. Incompatible cluster level
> b. VDSM version not supported.
>
> However, if we use this, it means that after every release of VDSM,
> we
> should update the SupportedVDSMVersions (i.e - add 4.9.6 to it)
> Is this what we want to do?
> The other option -as previously mentioned is to rely only on cluster
> compatibility level comparison (using the 'supprtedRHEVMs' reported
> by
> VDSM)
> Thoughts about this are more than welcome
>
> Yair
i agree with this approach,
just one fix, we should use vdsm's 'supportedProtocols'
which match the engine's cluster levels.
this way the versions of the software are not important,
only what 'protocols' (or cluster levels) are supported in both.
Is supportedProtocols ever used by Engine now? I think it is stale. I
resent introducing it, as the logic is too complex as it is. I think it
is enough to have a set of SupportedVDSMVersions, with the extra ability
to ship a vdsm with another version, reporting its supportedeRHEVMs.
It is unlikely that vdsm is ever shipped without a change to the
protocol (we are not in the business of reimplementation of old APIs).
So supportedProtocols is not going to change any slower than vdsm
version.
Please add vdsm-4.9.6 to the set of SupportedVDSMVersions.
7:56 a.m.
New subject: [Users] Host can't join the cluster
On 05/17/2012 11:30 AM, Itamar Heim wrote:
On 05/17/2012 11:28 AM, Omer Frenkel wrote:
>
>
> ----- Original Message -----
>> From: "Itamar Heim"<iheim(a)redhat.com>
>> To: "Dan Kenigsberg"<danken(a)redhat.com>
>> Cc: "Haim Ateya"<hateya(a)redhat.com>, users(a)ovirt.org, "Omer
>> Frenkel"<ofrenkel(a)redhat.com>
>> Sent: Wednesday, May 16, 2012 8:50:59 PM
>> Subject: Re: [Users] Host can't join the cluster
>>
>> On 05/16/2012 05:51 PM, Dan Kenigsberg wrote:
>>> How difficult would it be for Engine to handle the true
>>> version-release of vdsm?
>>>
>>> As a stop-gap measure, Engine could convert the reported
>>> version-release
>>> into the floating point numbers it can handle. The same stop-gap
>>> could
>>> be done on Vdsm side, but I consider this as a step backward.
IMHO, I
don't like this heck.
>>
>> why does engine cares about vdsm version, rather than compatibility
>> levels reported by vdsm?
>>
>
> the definition was, as i remember:
> vdsm reports which engine (cluster levels) it supports.
> engine reports which vdsm versions it supports.
> both must apply so a host would be active.
Not sure I understand why we need
both checks and not just cluster
compatibility level check?
well, first, then the error message is wrong and misleading (complains a
vdsm with compat levels of (3.0,3.1) can't join the cluster which is 3.1).
second, iirc, the definition was vdsm can override engine vdsm version
check, so a newer vdsm could still report it will work with an older
engine, without needing to change the older engine to match it?
>
>>>
>>> On Wed, May 16, 2012 at 09:59:42AM -0400, Haim Ateya wrote:
>>>> This issue was introduced in
>>>> Ic7b4a63a974bfc301f3294603d8fe91f534b74dd
>>>> (http://gerrit.ovirt.org/4284), we are currently working to
>>>> resolve this issue
>>>> and patch will be sent soon.
>>>> meantime, you can edit /usr/share/vdsm/dsaversion.py and change
>>>> the following fields:
>>>>
>>>> software_version = "4.9"
>>>> software_revision = "0
>>>>
>>>> restart vdsmd service and activate host again.
>>>>
>>>> Haim
>>>> ----- Original Message -----
>>>>
>>>>> From: ovirt(a)qip.ru
>>>>> To: "Haim Ateya"<hateya(a)redhat.com>
>>>>> Cc: users(a)ovirt.org
>>>>> Sent: Wednesday, May 16, 2012 3:19:04 PM
>>>>> Subject: Re: Re: [Users] Host can't join the cluster
>>>>
>>>>> in secure and non secure connections i have the same
>>>>> nonoperational
>>>>> status
>>>>
>>>>> the output of getVdsCaps on host is empty
>>>>
>>>>> this is event log in webadmin
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:04
>>>>
>>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>>>>> Cluster Default which is set to version 3.1.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:04
>>>>
>>>>> Detected new Host kvm04. Host state was set to Up.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:03
>>>>
>>>>> Host kvm04 was autorecovered.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:05:03
>>>>
>>>>> Host kvm04 is compatible with versions (3.0,3.1) and cannot join
>>>>> Cluster Default which is set to version 3.1.
>>>>
>>>>>
>>>>
>>>>> 2012-May-16, 16:01:02
>>>>
>>>>> Host kvm04 was activated by admin@internal.
>>>>> if i do downgrade to 4.9.6-0.196.gitb8b79b5 host state set's to
>>>>> Up.
>>>>
>>>>> Срд 16 Май 2012 15:24:36 +0400, Haim Ateya<hateya(a)redhat.com>
>>>>> написал:
>>>>
>>>>>> I guess you compiled vdsm yourself, please run the following
>>>>>> command
>>>>>> from your host:
>>>>>
>>>>
>>>>>> vdsClient -s 0 getVdsCaps (assuming you work with SSL).
>>>>>
>>>>
>>>>>> anyhow, it smells like a known issue with latest build where
>>>>>> vdsm
>>>>>> returns supported_clusters = 3.0 and engine reject host, but
>>>>>> lets
>>>>>> find out.
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:37 p.m.
This is a multi-part message in MIME format.
--------------070701010003040007070209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Usually, you can have more information in these files:
in node host:
/var/log/vdsm/log, /vdsm/log/libvirt.log
in engine:
/var/log/engine.log
On 2012-5-16 18:58, ovirt(a)qip.ru wrote:
After upgrade of vdsm from 4.9.6-0.196.gitb8b79b5 to
4.9.6-0.201.git98e8078
engine set host in nonoperational mode, the error is
"Host kvm04 is compatible with versions (3.0,3.1) and cannot join
Cluster Default which is set to version 3.1."
--
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Shu Ming<shuming(a)linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
--------------070701010003040007070209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Usually, you can have more information in these files:<br>
in node host:<br>
/var/log/vdsm/log, /vdsm/log/libvirt.log<br>
<br>
in engine:<br>
/var/log/engine.log<br>
<br>
<br>
<br>
On 2012-5-16 18:58, <a class="moz-txt-link-abbreviated"
href="mailto:ovirt@qip.ru">ovirt@qip.ru</a> wrote:
<blockquote
cite="mid:f5c7d8d154aea40052bdf82f63b42961371290bf@mail.qip.ru"
type="cite">After upgrade of vdsm from 4.9.6-0.196.gitb8b79b5
to
4.9.6-0.201.git98e8078<br>
<br>
engine set host in nonoperational mode, the error is<br>
<br>
<br>
<div title="" style="outline: medium none;">
<div id="gwt-uid-1204_col2_row6">"Host kvm04 is compatible
with
versions (3.0,3.1) and cannot join Cluster Default which is
set to version 3.1."</div>
</div>
<br>
<br>
--<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Shu Ming <a class="moz-txt-link-rfc2396E"
href="mailto:shuming@linux.vnet.ibm.com"><shuming@linux.vnet.ibm.com></a>
IBM China Systems and Technology Laboratory</pre>
</body>
</html>
--------------070701010003040007070209--
4604
days inactive
4610
days old
18 comments
7 participants
participants (7)
-
Dan Kenigsberg -
Haim Ateya -
Itamar Heim -
Omer Frenkel -
ovirt＠qip.ru -
Shu Ming -
Yair Zaslavsky