[Users] can't add hosts due to version compatibility with latest nightly

[Eli Mesika]

----- Original Message -----
> From: "Brian Vetter" <bjvetter at gmail.com>
> To: "Eli Mesika" <emesika at redhat.com>
> Cc: users at ovirt.org
> Sent: Monday, October 29, 2012 6:34:42 PM
> Subject: Re: [Users] can't add hosts due to version compatibility with latest nightly
> 
> Ugh. Nevermind. Something bogus was going on in Firefox. When I
> restarted it, those drop down fields started showing up.

Probably Firefox cache was holding your old drop down fields content...

> 
> Brian
> 
> On Oct 29, 2012, at 11:27 AM, Brian Vetter wrote:
> 
> > While there was a compatibility version field/selector provided in
> > the "new data center" dialog, it is empty - there is nothing to
> > select. Apparently, the default value is 3.2.
> > 
> > Brian
> > 
> > On Oct 29, 2012, at 10:04 AM, Eli Mesika wrote:
> > 
> >> 
> >> 
> >> ----- Original Message -----
> >>> From: "Brian Vetter" <bjvetter at gmail.com>
> >>> To: users at ovirt.org
> >>> Sent: Sunday, October 28, 2012 11:17:11 PM
> >>> Subject: [Users] can't add hosts due to version compatibility
> >>> with latest	nightly
> >>> 
> >>> 
> >>> 
> >>> I decided to start over and reinstall with the latest nightly
> >>> build.
> >>> When trying to get the system setup, I get the following error
> >>> when
> >>> trying to add a host.
> >>> 
> >>> 
> >>> 
> >>> 
> >>> Host mech is compatible with versions (3.0,3.1) and cannot join
> >>> Cluster DCCluster which is set to version 3.2
> >>> 
> >>> I saw no way to create a cluster for any other version (it only
> >>> provides a 3.2 choice in the drop down).
> >> 
> >> The reason is probably that you had created a 3.2 Data Center.
> >> If you will create a 3.1 Data Center , you should have the cluster
> >> as 3.1 as well
> >> 
> >>> 
> >>> 
> >>> I noticed that the vdsm rpms in the nightly repository were at
> >>> version 4.10.1-0.79 as opposed to the 4.10.0 version I saw on the
> >>> system after adding the host. On a lark, I logged into that
> >>> system
> >>> and tried installing/upgrading the vdsm version manually using
> >>> the
> >>> nightly build. When I tried this, I got an error saying that it
> >>> required libvirt >= 0.10.1-1. To get around that, I had to
> >>> download
> >>> all of the libvirt rpms for 0.10.1-1 (not in yum) and installed
> >>> them, and then upgraded vdsm.
> >>> 
> >>> 
> >>> I did seem to run into one issue - the system did not reboot on
> >>> its
> >>> own (ovirt had it in "reboot" mode). I had to log into the system
> >>> to
> >>> reboot it manually to get it to move to the next state and
> >>> activate.
> >>> 
> >>> 
> >>> So I have a few questions. Is the ovirt-engine supposed to push a
> >>> matching vdsm version (one that supports 3.2) to the host when it
> >>> is
> >>> added? If so, it doesn't appear to do that and instead it pushes
> >>> an
> >>> older one that was only 3.1 "compatible".
> >>> 
> >>> 
> >>> And if it should have pushed a newer version (possibly matching
> >>> the
> >>> nightly vdsm build), it seems like there is a push to use a newer
> >>> version of libvirt. I would presume that is coming in FC18. So
> >>> are
> >>> the current nightly builds expected to only run on a FC18 beta
> >>> type
> >>> release (which is supposedly coming soon)?
> >>> 
> >>> 
> >>> Brian
> >>> 
> >>> 
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users at ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>> 
> > 
> 
>