[Users] oVirt 3.1 - Error adding host , incorrect vdsm version
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. This is what's on the node vdsm.x86_64 4.10.0-0.33.git40b2d55.el6 @vdsm-dre vdsm-cli.noarch 4.10.0-0.33.git40b2d55.el6 @vdsm-dre vdsm-python.x86_64 4.10.0-0.33.git40b2d55.el6 @vdsm-dre vdsm-xmlrpc.noarch 4.10.0-0.33.git40b2d55.el6 @vdsm-dre Any advice? Thanks - Trey
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"
On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg <danken@redhat.com> wrote:
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"
Those changes worked, the install is now past that point and installing packages. Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201 Thanks - Trey
On Mon, Jun 18, 2012 at 04:08:06PM -0500, Trey Dockendorf wrote:
On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg <danken@redhat.com> wrote:
On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:
<snip>
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?
I actually really really hate the code there, and spent some time suggesting a less bad approach. Would you be kind enough to test http://gerrit.ovirt.org/#/c/5469/ and the 2 patches below it?
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"
Those changes worked, the install is now past that point and installing packages.
Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201
Thanks!
Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), and didn't encounter this issue at all. Danken - any idea why? ----- Original Message -----
On Mon, Jun 18, 2012 at 04:08:06PM -0500, Trey Dockendorf wrote:
On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg <danken@redhat.com> wrote:
On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:
<snip>
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?
I actually really really hate the code there, and spent some time suggesting a less bad approach. Would you be kind enough to test http://gerrit.ovirt.org/#/c/5469/ and the 2 patches below it?
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"
Those changes worked, the install is now past that point and installing packages.
Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201
Thanks! _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, Jun 19, 2012 at 12:08:09PM -0400, Ofer Schreiber wrote:
Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), and didn't encounter this issue at all.
Danken - any idea why?
Hey! I was the one soliciting ideas on how come this issue was not seen until Trey bumped on it. ;-) Maybe, just maybe, you host sees BOTH 4.10 and 4.9 ? what does the following print on your python interpreter? import yum my = yum.YumBase() my.pkgSack.searchNevra(name='rpm')
----- Original Message -----
On Mon, Jun 18, 2012 at 04:08:06PM -0500, Trey Dockendorf wrote:
On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg <danken@redhat.com> wrote:
On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:
<snip>
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?
I actually really really hate the code there, and spent some time suggesting a less bad approach. Would you be kind enough to test http://gerrit.ovirt.org/#/c/5469/ and the 2 patches below it?
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"
Those changes worked, the install is now past that point and installing packages.
Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201
Thanks! _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, Jun 19, 2012 at 1:40 PM, Dan Kenigsberg <danken@redhat.com> wrote: > On Tue, Jun 19, 2012 at 12:08:09PM -0400, Ofer Schreiber wrote: >> Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), and didn't encounter this issue at all. >> >> Danken - any idea why? > > Hey! I was the one soliciting ideas on how come this issue was not seen > until Trey bumped on it. ;-) > > Maybe, just maybe, you host sees BOTH 4.10 and 4.9 ? > > what does the following print on your python interpreter? > > import yum > my = yum.YumBase() > my.pkgSack.searchNevra(name='rpm') > > >> >> ----- Original Message ----- >> > On Mon, Jun 18, 2012 at 04:08:06PM -0500, Trey Dockendorf wrote: >> > > On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg <danken@redhat.com> >> > > wrote: >> > > >> > > > On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote: >> > >> > <snip> >> > >> > > > >> > > > 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? >> > >> > I actually really really hate the code there, and spent some time >> > suggesting a less bad approach. Would you be kind enough to test >> > http://gerrit.ovirt.org/#/c/5469/ >> > and the 2 patches below it? >> > >> > > > >> > > > 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" >> > > > >> > > > >> > > >> > > Those changes worked, the install is now past that point and >> > > installing >> > > packages. >> > > >> > > Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201 >> > >> > Thanks! >> > _______________________________________________ >> > Users mailing list >> > Users@ovirt.org >> > http://lists.ovirt.org/mailman/listinfo/users >> > >From the python , you want to output of name='rpm' or name='vdsm' ? I figured the later but included both On VDSM node >>> import yum >>> my = yum.YumBase() >>> my.pkgSack.searchNevra(name='rpm') Loaded plugins: fastestmirror, presto, priorities Loading mirror speeds from cached hostfile * base: mirror.raystedman.net * epel: mirror.utexas.edu * extras: mirror.unl.edu * updates: mirror.raystedman.net [<YumAvailablePackageSqlite : rpm-4.8.0-19.el6.x86_64 (0x28c49d0)>, <YumAvailablePackageSqlite : rpm-4.8.0-19.el6_2.1.x86_64 (0x28c4b90)>] >>> my.pkgSack.searchNevra(name='vdsm') [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 (0x28c4cd0)>] On the ovirt-engine host >>> import yum >>> my = yum.YumBase() >>> my.pkgSack.searchNevra(name='rpm') Loaded plugins: fastestmirror, priorities, versionlock Loading mirror speeds from cached hostfile * base: mirror.steadfast.net * epel: mirror.steadfast.net * extras: mirror.steadfast.net * updates: mirror.anl.gov [<YumAvailablePackageSqlite : rpm-4.8.0-19.el6.x86_64 (0x7f60110cedd0)>, <YumAvailablePackageSqlite : rpm-4.8.0-19.el6_2.1.x86_64 (0x7f60110dde90)>] >>> my.pkgSack.searchNevra(name='vdsm') [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 (0x7f60110dd490)>] Let me know if anything else would be helpful. Thanks - Trey
On Tue, Jun 19, 2012 at 02:43:14PM -0500, Trey Dockendorf wrote: > On Tue, Jun 19, 2012 at 1:40 PM, Dan Kenigsberg <danken@redhat.com> wrote: > > On Tue, Jun 19, 2012 at 12:08:09PM -0400, Ofer Schreiber wrote: > >> Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), and didn't encounter this issue at all. > >> > >> Danken - any idea why? > > > > Hey! I was the one soliciting ideas on how come this issue was not seen > > until Trey bumped on it. ;-) > > > > Maybe, just maybe, you host sees BOTH 4.10 and 4.9 ? > > > > what does the following print on your python interpreter? > > > > import yum > > my = yum.YumBase() > > my.pkgSack.searchNevra(name='rpm') > > > > >From the python , you want to output of name='rpm' or name='vdsm' ? I > figured the later but included both arghh s/rpm/vdsm/ Actually, this question was directed at Ofer. I was wodering how come the untouched code was working in his environment. > > On VDSM node > > >>> import yum > >>> my = yum.YumBase() > >>> my.pkgSack.searchNevra(name='rpm') > Loaded plugins: fastestmirror, presto, priorities > Loading mirror speeds from cached hostfile > * base: mirror.raystedman.net > * epel: mirror.utexas.edu > * extras: mirror.unl.edu > * updates: mirror.raystedman.net > [<YumAvailablePackageSqlite : rpm-4.8.0-19.el6.x86_64 (0x28c49d0)>, > <YumAvailablePackageSqlite : rpm-4.8.0-19.el6_2.1.x86_64 (0x28c4b90)>] > >>> my.pkgSack.searchNevra(name='vdsm') > [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 > (0x28c4cd0)>] > > > On the ovirt-engine host > > >>> import yum > >>> my = yum.YumBase() > >>> my.pkgSack.searchNevra(name='rpm') > Loaded plugins: fastestmirror, priorities, versionlock > Loading mirror speeds from cached hostfile > * base: mirror.steadfast.net > * epel: mirror.steadfast.net > * extras: mirror.steadfast.net > * updates: mirror.anl.gov > [<YumAvailablePackageSqlite : rpm-4.8.0-19.el6.x86_64 > (0x7f60110cedd0)>, <YumAvailablePackageSqlite : > rpm-4.8.0-19.el6_2.1.x86_64 (0x7f60110dde90)>] > >>> my.pkgSack.searchNevra(name='vdsm') > [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 > (0x7f60110dd490)>] > > Let me know if anything else would be helpful. Well, I could use yet another verification/review of my http://gerrit.ovirt.org/#/c/5469/ Thanks, Dan.
On Wed, Jun 20, 2012 at 05:58:57AM +0300, Dan Kenigsberg wrote:
On Tue, Jun 19, 2012 at 02:43:14PM -0500, Trey Dockendorf wrote:
On Tue, Jun 19, 2012 at 1:40 PM, Dan Kenigsberg <danken@redhat.com> wrote:
On Tue, Jun 19, 2012 at 12:08:09PM -0400, Ofer Schreiber wrote:
Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), and didn't encounter this issue at all.
Danken - any idea why?
Hey! I was the one soliciting ideas on how come this issue was not seen until Trey bumped on it. ;-)
Maybe, just maybe, you host sees BOTH 4.10 and 4.9 ?
what does the following print on your python interpreter?
import yum my = yum.YumBase() my.pkgSack.searchNevra(name='rpm')
From the python , you want to output of name='rpm' or name='vdsm' ? I figured the later but included both
arghh s/rpm/vdsm/
Actually, this question was directed at Ofer. I was wodering how come the untouched code was working in his environment.
For the record - we've tested this on Ofer's machine and found an old yum repo with vdsm-4.9.3 or something, which hidden this bug from many of us red-hatters. Thanks for reporting! The fix would be available in the next beta build.
I encountered this error in oVirt 3.1 beta release testing. And I changed the vdsm-bootstrap.py in engine similar to the below and it worked. I am also wondering why this bug was not exported to other people. It seems that ovirt node can ignore the vds_bootstrap script running on itself by someway. That maybe the reason the bug was not hit. On 2012-6-20 0:08, Ofer Schreiber wrote: > Just checked this issue with latest ovirt-engine on F17 (with vdsm 4.10), and didn't encounter this issue at all. > > Danken - any idea why? > > ----- Original Message ----- >> On Mon, Jun 18, 2012 at 04:08:06PM -0500, Trey Dockendorf wrote: >>> On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg<danken@redhat.com> >>> wrote: >>> >>>> On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote: >> <snip> >> >>>> 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? >> I actually really really hate the code there, and spent some time >> suggesting a less bad approach. Would you be kind enough to test >> http://gerrit.ovirt.org/#/c/5469/ >> and the 2 patches below it? >> >>>> 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" >>>> >>>> >>> Those changes worked, the install is now past that point and >>> installing >>> packages. >>> >>> Bug filed, https://bugzilla.redhat.com/show_bug.cgi?id=833201 >> Thanks! >> _______________________________________________ >> 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 > -- Shu Ming<shuming@linux.vnet.ibm.com> IBM China Systems and Technology Laboratory
This is a multi-part message in MIME format. --------------000000060704080905020606 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit You might want to disable InstallVds and restart the engine. Since it will attempt to install the packages from yum and that could cause an issue if you are installing hand built RPM. psql engine -U postgres -c "UPDATE vdc_options set option_value = 'false' where option_name = 'InstallVds'" service ovirt-engine restart On 06/18/2012 04:01 PM, 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 <http://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.
This is what's on the node vdsm.x86_64 4.10.0-0.33.git40b2d55.el6 @vdsm-dre vdsm-cli.noarch 4.10.0-0.33.git40b2d55.el6 @vdsm-dre vdsm-python.x86_64 4.10.0-0.33.git40b2d55.el6 @vdsm-dre vdsm-xmlrpc.noarch 4.10.0-0.33.git40b2d55.el6 @vdsm-dre
Any advice?
Thanks - Trey
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------000000060704080905020606 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 text="#000000" bgcolor="#FFFFFF"> You might want to disable InstallVds and restart the engine. Since it will attempt to install the packages from yum and that could cause an issue if you are installing hand built RPM.<br> <br> psql engine -U postgres -c "UPDATE vdc_options set option_value = 'false' where option_name = 'InstallVds'"<br> service ovirt-engine restart<br> <br> <br> On 06/18/2012 04:01 PM, Trey Dockendorf wrote: <blockquote cite="mid:CAN0oX1YO=8FacdJQKrAp=O3kKT7xyNmhw3rZYHiGy7XxWi2Zgw@mail.gmail.com" type="cite"> <div style="text-align:left">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</div> <div style="text-align:left"><br> </div> <div style="text-align:left"> <div>ovirt-engine.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-backend.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-config.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-dbscripts.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-genericapi.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-jbossas711.x86_64 1-0 @ovirt-dre</div> <div>ovirt-engine-notification-service.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-restapi.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-sdk.noarch 3.1.0.1-1alpha.el6 @ovirt-dre</div> <div>ovirt-engine-setup.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-tools-common.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-userportal.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-engine-webadmin-portal.noarch 3.1.0_0001-1.8.el6 @ovirt-dre</div> <div>ovirt-image-uploader.noarch 1.0.0-1.el6 @ovirt-dre</div> <div>ovirt-iso-uploader.noarch 1.0.0-1.el6 @ovirt-dre</div> <div>ovirt-log-collector.noarch 1.0.0-1.el6 @ovirt-dre</div> </div> <div style="text-align:left"><br> </div> <div style="text-align:left"><br> </div> <div style="text-align:left">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"</div> <div style="text-align:left"><br> </div> <div style="text-align:left">on the node , /tmp/vds_bootstrap.64713.log</div> <div style="text-align:left"> <div>Mon, 18 Jun 2012 14:20:20 DEBUG **** Start VDS Validation ****</div> <div>Mon, 18 Jun 2012 14:20:20 DEBUG Entered VdsValidation(subject = '<a moz-do-not-send="true" href="http://dc-kvm0.tamu.edu">dc-kvm0.tamu.edu</a>', random_num = '8408ad00-510d-47a7-98e9-ed73d95ad85d', rev_num = 'None', installVirtualizationService = 'True', installGlusterService = 'False')</div> <div>Mon, 18 Jun 2012 14:20:20 DEBUG Setting up Package Sacks</div> <div>Mon, 18 Jun 2012 14:20:22 DEBUG yumSearch: found vdsm entries: [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 (0x17e8e90)>]</div> <div>Mon, 18 Jun 2012 14:20:22 DEBUG Host properly registered with RHN/Satellite.</div> <div>Mon, 18 Jun 2012 14:20:22 DEBUG <BSTRAP component='RHN_REGISTRATION' status='OK' message='Host properly registered with RHN/Satellite.'/></div> <div>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</div> <div>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</div> <div>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'/></div> <div>Mon, 18 Jun 2012 14:20:25 ERROR checkMajorVersion test failed</div> <div>Mon, 18 Jun 2012 14:20:25 DEBUG <BSTRAP component='RHEV_INSTALL' status='FAIL'/></div> <div>Mon, 18 Jun 2012 14:20:25 DEBUG **** End VDS Validation ****</div> <div><br> </div> <div><br> </div> <div>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.</div> </div> <div style="text-align:left"><br> </div> <div style="text-align:left">This is what's on the node</div> <div style="text-align:left"> <div>vdsm.x86_64 4.10.0-0.33.git40b2d55.el6 @vdsm-dre</div> <div>vdsm-cli.noarch 4.10.0-0.33.git40b2d55.el6 @vdsm-dre</div> <div>vdsm-python.x86_64 4.10.0-0.33.git40b2d55.el6 @vdsm-dre</div> <div>vdsm-xmlrpc.noarch 4.10.0-0.33.git40b2d55.el6 @vdsm-dre</div> <div><br> </div> <div>Any advice? </div> <div><br> </div> <div>Thanks</div> <div>- Trey</div> </div> <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://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------000000060704080905020606--
participants (5)
-
Dan Kenigsberg -
Ofer Schreiber -
Robert Middleswarth -
Shu Ming -
Trey Dockendorf