<br><br><div class="gmail_quote">On Mon, Jun 18, 2012 at 3:25 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Mon, Jun 18, 2012 at 03:01:10PM -0500, Trey Dockendorf wrote:<br>
> I have a ovirt-3.1 server installed in CentOS 6.2 via the ovirt-dre repo ,<br>
> this is what is installed on the server with ovirt-engine<br>
><br>
> ovirt-engine.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-backend.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-config.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-dbscripts.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-genericapi.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-jbossas711.x86_64<br>
> 1-0<br>
> @ovirt-dre<br>
> ovirt-engine-notification-service.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-restapi.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-sdk.noarch<br>
> 3.1.0.1-1alpha.el6<br>
> @ovirt-dre<br>
> ovirt-engine-setup.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-tools-common.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-userportal.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-engine-webadmin-portal.noarch<br>
> 3.1.0_0001-1.8.el6<br>
> @ovirt-dre<br>
> ovirt-image-uploader.noarch<br>
> 1.0.0-1.el6<br>
> @ovirt-dre<br>
> ovirt-iso-uploader.noarch<br>
> 1.0.0-1.el6<br>
> @ovirt-dre<br>
> ovirt-log-collector.noarch<br>
> 1.0.0-1.el6<br>
> @ovirt-dre<br>
><br>
><br>
> I took an existing KVM server and installed vdsm and follow both the Dreyou<br>
> instructions and those in ovirt documentation on setting up a node.<br>
> However when I add the node via ovirt management portal I get an error in<br>
> the GUI on the step for "VDSM_MAJOR_VER"<br>
><br>
> on the node , /tmp/vds_bootstrap.64713.log<br>
> Mon, 18 Jun 2012 14:20:20 DEBUG **** Start VDS Validation ****<br>
> Mon, 18 Jun 2012 14:20:20 DEBUG Entered VdsValidation(subject = '<br>
> <a href="http://dc-kvm0.tamu.edu" target="_blank">dc-kvm0.tamu.edu</a>', random_num = '8408ad00-510d-47a7-98e9-ed73d95ad85d',<br>
> rev_num = 'None', installVirtualizationService = 'True',<br>
> installGlusterService = 'False')<br>
> Mon, 18 Jun 2012 14:20:20 DEBUG Setting up Package Sacks<br>
> Mon, 18 Jun 2012 14:20:22 DEBUG yumSearch: found vdsm entries:<br>
> [<YumAvailablePackageSqlite : vdsm-4.10.0-0.33.git40b2d55.el6.x86_64<br>
> (0x17e8e90)>]<br>
> Mon, 18 Jun 2012 14:20:22 DEBUG Host properly registered with<br>
> RHN/Satellite.<br>
> Mon, 18 Jun 2012 14:20:22 DEBUG <BSTRAP component='RHN_REGISTRATION'<br>
> status='OK' message='Host properly registered with RHN/Satellite.'/><br>
> Mon, 18 Jun 2012 14:20:25 DEBUG yumSearchVersion: pkg<br>
> vdsm-4.10.0-0.33.git40b2d55.el6.x86_64 does not start with: vdsm-4.9<br>
> Mon, 18 Jun 2012 14:20:25 ERROR Unable to fetch VDSM with minimal<br>
> version of vdsm-4.9. Please check if host is properly registered with<br>
> updated yum repository<br>
> Mon, 18 Jun 2012 14:20:25 DEBUG <BSTRAP component='VDSM_MAJOR_VER'<br>
> status='FAIL' message='Unable to fetch VDSM with minimal version of<br>
> vdsm-4.9. Please check if host is properly registered with updated yum<br>
> repository'/><br>
> Mon, 18 Jun 2012 14:20:25 ERROR checkMajorVersion test failed<br>
> Mon, 18 Jun 2012 14:20:25 DEBUG <BSTRAP component='RHEV_INSTALL'<br>
> status='FAIL'/><br>
> Mon, 18 Jun 2012 14:20:25 DEBUG **** End VDS Validation ****<br>
><br>
><br>
> This is a rather obvious error, it expects vdsm-4.9* and I have vdsm-4.10*.<br>
> Is this a bug or expected? I'd seem to think it's a bug as the beta repo<br>
> for ovirt has ovirt-3.1 with vdsm-4.10.<br>
<br>
</div></div>You are right. And it is truly surprising that this bug hasn't been<br>
open since we've bumped vdsm version to 4.10.<br>
<br>
Would you open up this bug, and make it block<br>
Bug 822145 - Tracker: oVirt 3.1 release<br>
?<br>
<br>
The bootstrapping code is a mess. It evolves by adding one ugly patch<br>
over the other. In that spirit, would the following patch solve your<br>
bootstrapping pains?<br>
<br>
diff --git a/vds_bootstrap/vds_bootstrap.py b/vds_bootstrap/vds_bootstrap.py<br>
index 0df5023..4fcc040 100755<br>
--- a/vds_bootstrap/vds_bootstrap.py<br>
+++ b/vds_bootstrap/vds_bootstrap.py<br>
@@ -76,11 +76,11 @@ rhel6based = deployUtil.versionCompare(deployUtil.getOSVersion(), "6.0") >= 0<br>
<br>
# TODO this is an infra-hackish heuristic for identifying Fedora<br>
# drop as soon as possible<br>
-fedorabased = deployUtil.versionCompare(deployUtil.getOSVersion(), "16") >= 0<br>
+fedorabased = deployUtil.versionCompare(deployUtil.getOSVersion(), "17") >= 0<br>
<br>
if rhel6based:<br>
VDSM_NAME = "vdsm"<br>
- VDSM_MIN_VER = VDSM_NAME + "-4.9"<br>
+ VDSM_MIN_VER = VDSM_NAME + "-4.10"<br>
KERNEL_VER = "2.6.32-.*.el6"<br>
KERNEL_MIN_VER = 150<br>
MINIMAL_SUPPORTED_PLATFORM = "6.0"<br>
<br>
</blockquote></div><br><div><br></div><div>Those changes worked, the install is now past that point and installing packages.</div><div><br></div><div>Bug filed, <a href="https://bugzilla.redhat.com/show_bug.cgi?id=833201">https://bugzilla.redhat.com/show_bug.cgi?id=833201</a></div>
<div><br></div><div>Thanks</div><div>- Trey</div>