[Users] oVirt 3.1 - Error adding host , incorrect vdsm version

[Dan Kenigsberg]

On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:
> I have a ovirt-3.1 server installed in CentOS 6.2 via the ovirt-dre repo ,
> this is what is installed on the server with ovirt-engine
> 
> ovirt-engine.noarch
>                      3.1.0_0001-1.8.el6
>                      @ovirt-dre
> ovirt-engine-backend.noarch
>                      3.1.0_0001-1.8.el6
>                      @ovirt-dre
> ovirt-engine-config.noarch
>                       3.1.0_0001-1.8.el6
>                        @ovirt-dre
> ovirt-engine-dbscripts.noarch
>                      3.1.0_0001-1.8.el6
>                      @ovirt-dre
> ovirt-engine-genericapi.noarch
>                       3.1.0_0001-1.8.el6
>                        @ovirt-dre
> ovirt-engine-jbossas711.x86_64
>                       1-0
>                       @ovirt-dre
> ovirt-engine-notification-service.noarch
>                       3.1.0_0001-1.8.el6
>                        @ovirt-dre
> ovirt-engine-restapi.noarch
>                      3.1.0_0001-1.8.el6
>                      @ovirt-dre
> ovirt-engine-sdk.noarch
>                      3.1.0.1-1alpha.el6
>                      @ovirt-dre
> ovirt-engine-setup.noarch
>                      3.1.0_0001-1.8.el6
>                      @ovirt-dre
> ovirt-engine-tools-common.noarch
>                       3.1.0_0001-1.8.el6
>                        @ovirt-dre
> ovirt-engine-userportal.noarch
>                       3.1.0_0001-1.8.el6
>                        @ovirt-dre
> ovirt-engine-webadmin-portal.noarch
>                      3.1.0_0001-1.8.el6
>                      @ovirt-dre
> ovirt-image-uploader.noarch
>                      1.0.0-1.el6
>                       @ovirt-dre
> ovirt-iso-uploader.noarch
>                      1.0.0-1.el6
>                       @ovirt-dre
> ovirt-log-collector.noarch
>                       1.0.0-1.el6
>                       @ovirt-dre
> 
> 
> I took an existing KVM server and installed vdsm and follow both the Dreyou
> instructions and those in ovirt documentation on setting up a node.
>  However when I add the node via ovirt management portal I get an error in
> the GUI on the step for "VDSM_MAJOR_VER"
> 
> on the node , /tmp/vds_bootstrap.64713.log
> Mon, 18 Jun 2012 14:20:20 DEBUG    **** Start VDS Validation ****
> Mon, 18 Jun 2012 14:20:20 DEBUG    Entered VdsValidation(subject = '
> dc-kvm0.tamu.edu', random_num = '8408ad00-510d-47a7-98e9-ed73d95ad85d',
> rev_num = 'None', installVirtualizationService = 'True',
> installGlusterService = 'False')
> Mon, 18 Jun 2012 14:20:20 DEBUG    Setting up Package Sacks
> Mon, 18 Jun 2012 14:20:22 DEBUG    yumSearch: found vdsm entries:
> [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64
> (0x17e8e90)>]
> Mon, 18 Jun 2012 14:20:22 DEBUG    Host properly registered with
> RHN/Satellite.
> Mon, 18 Jun 2012 14:20:22 DEBUG    <BSTRAP component='RHN_REGISTRATION'
> status='OK' message='Host properly registered with RHN/Satellite.'/>
> Mon, 18 Jun 2012 14:20:25 DEBUG    yumSearchVersion: pkg
> vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 does not start with: vdsm-4.9
> Mon, 18 Jun 2012 14:20:25 ERROR    Unable to fetch VDSM with minimal
> version of vdsm-4.9. Please check if host is properly registered with
> updated yum repository
> Mon, 18 Jun 2012 14:20:25 DEBUG    <BSTRAP component='VDSM_MAJOR_VER'
> status='FAIL' message='Unable to fetch VDSM with minimal version of
> vdsm-4.9. Please check if host is properly registered with updated yum
> repository'/>
> Mon, 18 Jun 2012 14:20:25 ERROR    checkMajorVersion test failed
> Mon, 18 Jun 2012 14:20:25 DEBUG    <BSTRAP component='RHEV_INSTALL'
> status='FAIL'/>
> Mon, 18 Jun 2012 14:20:25 DEBUG    **** End VDS Validation ****
> 
> 
> This is a rather obvious error, it expects vdsm-4.9* and I have vdsm-4.10*.
>  Is this a bug or expected?  I'd seem to think it's a bug as the beta repo
> for ovirt has ovirt-3.1 with vdsm-4.10.

You are right. And it is truly surprising that this bug hasn't been
open since we've bumped vdsm version to 4.10.

Would you open up this bug, and make it block
    Bug 822145 - Tracker: oVirt 3.1 release
?

The bootstrapping code is a mess. It evolves by adding one ugly patch
over the other. In that spirit, would the following patch solve your
bootstrapping pains?

diff --git a/vds_bootstrap/vds_bootstrap.py b/vds_bootstrap/vds_bootstrap.py
index 0df5023..4fcc040 100755
--- a/vds_bootstrap/vds_bootstrap.py
+++ b/vds_bootstrap/vds_bootstrap.py
@@ -76,11 +76,11 @@ rhel6based = deployUtil.versionCompare(deployUtil.getOSVersion(), "6.0") >= 0
 
 # TODO this is an infra-hackish heuristic for identifying Fedora
 # drop as soon as possible
-fedorabased = deployUtil.versionCompare(deployUtil.getOSVersion(), "16") >= 0
+fedorabased = deployUtil.versionCompare(deployUtil.getOSVersion(), "17") >= 0
 
 if rhel6based:
     VDSM_NAME = "vdsm"
-    VDSM_MIN_VER = VDSM_NAME + "-4.9"
+    VDSM_MIN_VER = VDSM_NAME + "-4.10"
     KERNEL_VER = "2.6.32-.*.el6"
     KERNEL_MIN_VER = 150
     MINIMAL_SUPPORTED_PLATFORM = "6.0"