[Users] compatibility issue
--_000_9BE6F493F83A594DA60C45E6A09DC5AC01763742AUSP01DAG0201co_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Just got 3.2 installed as ovirt node on a fedora 18 install. After the reb= oot, the console now complains with this: 2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and cann= ot join Cluster Default which is set to version 3.2. 2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple interf= aces: <UNKNOWN> on Host rnd8. The server (rnd8) is a dell 2950 with dual X5460 processors. I never had t= o mess with this type of thing in the past on 3.1, is there something I did= not configure on 3.2 that is causing this? Is a dell 2950 not supported o= n 3.2? Thanks, jonathan ________________________________ This is a PRIVATE message. If you are not the intended recipient, please de= lete without copying and kindly advise us by e-mail of the mistake in deliv= ery. NOTE: Regardless of content, this e-mail shall not operate to bind SKO= POS to any order or other contract unless pursuant to explicit written agre= ement or government initiative expressly permitting the use of e-mail for s= uch purpose. --_000_9BE6F493F83A594DA60C45E6A09DC5AC01763742AUSP01DAG0201co_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
<style> <!-- @font-face {font-family:Calibri} @font-face {font-family:Tahoma} p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif"} a:link, span.MsoHyperlink {color:blue; text-decoration:underline} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate {margin:0in; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif"} span.EmailStyle17 {font-family:"Calibri","sans-serif"; color:windowtext} span.BalloonTextChar {font-family:"Tahoma","sans-serif"} .MsoChpDefault {font-family:"Calibri","sans-serif"} @page WordSection1 {margin:1.0in 1.0in 1.0in 1.0in} div.WordSection1 {} --> </style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Just got 3.2 installed as ovirt node on a fedora 18 = install. After the reboot, the console now complains with this:</p> <p class=3D"MsoNormal"> </p> <p class=3D"MsoNormal"> &nbs= p; </p> <p class=3D"MsoNormal">2013-Feb-18, 12:20 Host rnd8 is compatible with vers= ions (3.0,3.1) and cannot join Cluster Default which is set to version 3.2.= </p> <p class=3D"MsoNormal">2013-Feb-18, 12:20 Bridged network ovirtmgmt is atta= ched to multiple interfaces: <UNKNOWN> on Host rnd8.</p> <p class=3D"MsoNormal"> </p> <p class=3D"MsoNormal">The server (rnd8) is a dell 2950 with dual X54= 60 processors. I never had to mess with this type of thing in the past on 3= .1, is there something I did not configure on 3.2 that is causing this?&nbs= p; Is a dell 2950 not supported on 3.2?</p> <p class=3D"MsoNormal"> </p> <p class=3D"MsoNormal">Thanks,</p> <p class=3D"MsoNormal">jonathan</p> </div> <br> <hr> <font color=3D"Gray" face=3D"Arial" size=3D"1">This is a PRIVATE message. I= f you are not the intended recipient, please delete without copying and kin= dly advise us by e-mail of the mistake in delivery. NOTE: Regardless of con= tent, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit wri= tten agreement or government initiative expressly permitting the use of e-m= ail for such purpose.</font> </body> </html> --_000_9BE6F493F83A594DA60C45E6A09DC5AC01763742AUSP01DAG0201co_--
On Mon, Feb 18, 2013 at 7:27 PM, Jonathan Horne <jhorne@skopos.us> wrote:
Just got 3.2 installed as ovirt node on a fedora 18 install. After the reboot, the console now complains with this:
2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and cannot join Cluster Default which is set to version 3.2.
2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple interfaces: <UNKNOWN> on Host rnd8.
The server (rnd8) is a dell 2950 with dual X5460 processors. I never had to mess with this type of thing in the past on 3.1, is there something I did not configure on 3.2 that is causing this? Is a dell 2950 not supported on 3.2?
Thanks,
jonathan
At a certain point during 3.2 development the default became 3.2. What version is your engine? Did you install ex-novo the engine and the node? Did you perhaps reuse an ip that for some reason is already allocated in db as 3.1 host? Probably not me, but others can help you if you give full details of environment and logs... Gianluca
Both the manager and the node are fresh installs of fedora 18, and the node ovirt install was initiated from the web console (so I don’t see how its possible I have a downlevel version on the node). -----Original Message----- From: Gianluca Cecchi [mailto:gianluca.cecchi@gmail.com] Sent: Monday, February 18, 2013 1:12 PM To: Jonathan Horne Cc: users@ovirt.org Subject: Re: [Users] compatibility issue On Mon, Feb 18, 2013 at 7:27 PM, Jonathan Horne <jhorne@skopos.us> wrote:
Just got 3.2 installed as ovirt node on a fedora 18 install. After the reboot, the console now complains with this:
2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and cannot join Cluster Default which is set to version 3.2.
2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple interfaces: <UNKNOWN> on Host rnd8.
The server (rnd8) is a dell 2950 with dual X5460 processors. I never had to mess with this type of thing in the past on 3.1, is there something I did not configure on 3.2 that is causing this? Is a dell 2950 not supported on 3.2?
Thanks,
jonathan
At a certain point during 3.2 development the default became 3.2. What version is your engine? Did you install ex-novo the engine and the node? Did you perhaps reuse an ip that for some reason is already allocated in db as 3.1 host? Probably not me, but others can help you if you give full details of environment and logs... Gianluca ________________________________ This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Did you add the ovirt repo to the node before deploying it? If not then you may have the older vdsm from the fedora repo. --- Jeff On 2/18/2013 5:06 PM, Jonathan Horne wrote:
Both the manager and the node are fresh installs of fedora 18, and the node ovirt install was initiated from the web console (so I don’t see how its possible I have a downlevel version on the node).
-----Original Message----- From: Gianluca Cecchi [mailto:gianluca.cecchi@gmail.com] Sent: Monday, February 18, 2013 1:12 PM To: Jonathan Horne Cc: users@ovirt.org Subject: Re: [Users] compatibility issue
On Mon, Feb 18, 2013 at 7:27 PM, Jonathan Horne <jhorne@skopos.us> wrote:
Just got 3.2 installed as ovirt node on a fedora 18 install. After the reboot, the console now complains with this:
2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and cannot join Cluster Default which is set to version 3.2.
2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple interfaces: <UNKNOWN> on Host rnd8.
The server (rnd8) is a dell 2950 with dual X5460 processors. I never had to mess with this type of thing in the past on 3.1, is there something I did not configure on 3.2 that is causing this? Is a dell 2950 not supported on 3.2?
Thanks,
jonathan
At a certain point during 3.2 development the default became 3.2. What version is your engine? Did you install ex-novo the engine and the node? Did you perhaps reuse an ip that for some reason is already allocated in db as 3.1 host?
Probably not me, but others can help you if you give full details of environment and logs...
Gianluca
________________________________ This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Ah, thank you! This was the problem, I did not have the ovirt repo on my node. The 3.2 node has activated properly now! Thanks, jonathan -----Original Message----- From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Jeff Bailey Sent: Monday, February 18, 2013 5:09 PM To: users@ovirt.org Subject: Re: [Users] compatibility issue Did you add the ovirt repo to the node before deploying it? If not then you may have the older vdsm from the fedora repo. --- Jeff On 2/18/2013 5:06 PM, Jonathan Horne wrote:
Both the manager and the node are fresh installs of fedora 18, and the node ovirt install was initiated from the web console (so I don’t see how its possible I have a downlevel version on the node).
-----Original Message----- From: Gianluca Cecchi [mailto:gianluca.cecchi@gmail.com] Sent: Monday, February 18, 2013 1:12 PM To: Jonathan Horne Cc: users@ovirt.org Subject: Re: [Users] compatibility issue
On Mon, Feb 18, 2013 at 7:27 PM, Jonathan Horne <jhorne@skopos.us> wrote:
Just got 3.2 installed as ovirt node on a fedora 18 install. After the reboot, the console now complains with this:
2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and cannot join Cluster Default which is set to version 3.2.
2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple interfaces: <UNKNOWN> on Host rnd8.
The server (rnd8) is a dell 2950 with dual X5460 processors. I never had to mess with this type of thing in the past on 3.1, is there something I did not configure on 3.2 that is causing this? Is a dell 2950 not supported on 3.2?
Thanks,
jonathan
At a certain point during 3.2 development the default became 3.2. What version is your engine? Did you install ex-novo the engine and the node? Did you perhaps reuse an ip that for some reason is already allocated in db as 3.1 host?
Probably not me, but others can help you if you give full details of environment and logs...
Gianluca
________________________________ This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ________________________________ This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
On 02/18/2013 08:27 PM, Jonathan Horne wrote:
Just got 3.2 installed as ovirt node on a fedora 18 install. After the reboot, the console now complains with this:
2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and cannot join Cluster Default which is set to version 3.2.
Probably the vdsm version on the node doesn't support 3.2 clusters and needed to be updated. You can see the supported cluster versions by running the following on the node: vdsClient -s 0 getVdsCaps | grep clusterLevels
2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple interfaces: <UNKNOWN> on Host rnd8.
This warning is as a result of the ovirtmgmt network configured on top of two interfaces. (The <UNKNOWN> bug was replaced with the actual nics name yesterday on commit bd56be79a4e1c5a873a65bf41adbcffef05cbde2). ovirt doesn't support this type of network configuration. You should remove one of the nics manually from the bridge, by running on the host: #to examine which interfaces are used for the management network brctl show ovirtmgmt # in order to remove on of the nics brctl delif ovirtmgmt one_of_the_nics
The server (rnd8) is a dell 2950 with dual X5460 processors. I never had to mess with this type of thing in the past on 3.1, is there something I did not configure on 3.2 that is causing this? Is a dell 2950 not supported on 3.2?
Thanks,
jonathan
------------------------------------------------------------------------ This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
Gianluca Cecchi -
Jeff Bailey -
Jonathan Horne -
Moti Asayag