Bug 918109 - Failed to add host - does not accept vdsm 4.10
Summary: Failed to add host - does not accept vdsm 4.10
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.1.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: 3.2.0
Assignee: Douglas Schilling Landgraf
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On: 833201
Blocks: 822145
TreeView+ depends on / blocked
 
Reported: 2013-03-05 13:54 UTC by Stefanie Forrester
Modified: 2016-02-10 19:21 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 833201
Environment:
Last Closed:
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stefanie Forrester 2013-03-05 13:54:06 UTC
+++ This bug was initially created as a clone of Bug #833201 +++

Description of problem:

When adding a host through the web interface the bootstrap process fails on the node that the VDSM version is incorrect.


Version-Release number of selected component (if applicable):

ovirt-engine-3.1-beta
vdsm-4.10.0-0.33.git40b2d55


How reproducible:

Every time

Steps to Reproduce:
1. Install vdsm 4.10* to node
2. Attempt to add node via engine interface

  
Actual results:

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 ****


Expected results:

Node is successfully added to oVirt

Additional info:

--- Additional comment from Trey Dockendorf on 2012-06-18 17:17:34 EDT ---

Patch provided by by Dan Kenigsberg here , http://lists.ovirt.org/pipermail/users/2012-June/002468.html, solved the issue.  Host was successfully added after the patch to vds_bootstrap.py.

--- Additional comment from Itamar Heim on 2012-06-19 00:05:51 EDT ---

why is this patch correct?
what if i want to install a vdsm-4.9 (3.0 compatibility level) on the host?

--- Additional comment from Dan Kenigsberg on 2012-06-19 03:43:31 EDT ---

(In reply to comment #2)
> why is this patch correct?
> what if i want to install a vdsm-4.9 (3.0 compatibility level) on the host?

I really hate the patch (even though I think it is good enough for ovirt-3.1)

I've posted another patch which is slightly saner.

http://gerrit.ovirt.org/#/c/5469/

--- Additional comment from Federico Simoncelli on 2012-06-22 07:54:22 EDT ---

In the ovirt-3.1 branch as: 67309fc8a7a4edd4996490b64f51ce37f0ed2327

--- Additional comment from Itamar Heim on 2012-08-09 04:05:43 EDT ---

closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/

--- Additional comment from Stefanie Edgar on 2013-03-04 20:02:12 EST ---

Hi,

I was having this issue in RHEV 3.0, so today I upgraded to 3.1. The issue still appears to be present, since I'm unable to add any RHEL hosts through the RHEV Manager. 

I'm not getting the entire error listed above, but I am receiving this part:

"Unable to fetch VDSM with minimal version of vdsm-4.9."

The RHN-checks seem to return successfully, but it fails the next step:

Received message: <BSTRAP component='RHN_REGISTRATION' status='OK' message='Host properly registered with RHN/Satellite.'/>. FYI. (Stage: Running first installation script on Host)
2013-03-04 19:22:21,456 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-11) Installation of 10.16.67.136. Received message: <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'/>. FYI. (Stage: Running first installation script on Host)
2013-03-04 19:22:21,656 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-11) Installation of 10.16.67.136. Received message: <BSTRAP component='RHEV_INSTALL' status='FAIL'/>. Error occured. (Stage: Running first installation script on Host)


The hypervisor has vdsm version 4.10.2-1.6.el6.x86_64 available in its repos. And the RHEV Manager has vdsm-bootstrap-4.9.6-45.2.el6_3.noarch installed. I am using some internal repositories, but I've been told they mirror RHN.

For RHEVM:
http://download.devel.redhat.com/sysrepos/rhel6-server-rhevm-3.1-x86_64/RPMS.rhevm_3.1/

For the hypervisor:
http://download.devel.redhat.com/sysrepos/rhel6-rhev-mgmt-agent-6-x86_64/RPMS.agent_6/

I tested adding a RHEVH host to this RHEV instance, and it worked. So it's only affecting the regular RHEL hosts, which are most likely still having issues with vdsm version compatibility.

--- Additional comment from Dan Kenigsberg on 2013-03-05 02:58:37 EST ---

I believe that this issue was indeed solved by ovirt commit http://gerrit.ovirt.org/5544 . So keeping this bug closed is correct.

However, in order to get the fixed code into rhev-3.1.z, you would have to upgrade the vdsm-bootstrap.rpm that is installed on your rhev-m machine. Does this solve the issue?

If this does not help, please clone this bug to the RHEV-M-3.1 project.

Comment 1 Dan Kenigsberg 2013-03-05 16:06:15 UTC
Please try installing the most recent vdsm-bootstrap-4.10.2-1.6 on your Engine host and report if this solves the issue.

Comment 2 Stefanie Forrester 2013-03-05 16:43:44 UTC
Correct me if I'm wrong, but RHN does not seem to contain an updated version of vdsm-bootstrap.

https://access.redhat.com/search/results/?col=avalon_portal&quickSearch=vdsm-bootstrap&start=0&facets=&language=en&cid=3897249

It's certainly nowhere to be found in my RHN mirror repos, and two other people have also reported that using an actual RHN subscription only yields vdsm-bootstrap-4.9.6-45.2.

Comment 3 Itamar Heim 2013-03-05 16:57:23 UTC
Stefanie - can you please check if the rpm danken mentioned solves the issue for you (then we can look at rhn aspect).

Comment 4 Stefanie Forrester 2013-03-05 17:36:00 UTC
Yes, that package did get further than the one from RHN. It passes the VDSM version test now.


2013-03-05 12:14:02,760 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:05,430 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='SET_SYSTEM_TIME' status='OK' message='setSystemTime ended successfully'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:09,700 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='RHN_REGISTRATION' status='OK' message='Host properly registered with RHN/Satellite.'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:09,789 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='VDSM_MAJOR_VER' status='OK' message='Available VDSM matches requirements'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:09,899 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='VT_SVM' status='OK' processor='Intel' message='Server supports virtualization'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:10,007 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='OS' status='OK' type='RHEL6' message='Supported platform version'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:10,118 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='KERNEL' status='OK' version='2.6.32-358.0.1.el6.x86_64' message='Supported kernel version: [~2.6.32~, ~358.0.1.el6.x86_64~]'/>. FYI. (Stage: Running first installation script on Host)
2013-03-05 12:14:11,471 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-25) Installation of 10.16.67.136. Received message: <BSTRAP component='PACKAGES' status='OK' result='yum' message='Status: Downloading Packages'/>. FYI. (Stage: Running first installation script on Host)

It does fail eventually, after some package installations, but I think that's because I need to update some related packages to version 4.10.2-1.6. RHN has only the older 4.9.6-45.2 packages, which may not work with the updated vdsm-bootstrap.

Comment 6 Stefanie Forrester 2013-03-05 21:49:20 UTC
dougsland assisted me with some debugging, and we figured out that the additional errors I was seeing were based on my specific environment settings (not related to this bug). So the original error has been fixed by vdsm-bootstrap-4.10.2-1.6, as suggested. 

We still need to find a way to get vdsm-bootstrap-4.10.2-1.6 into RHN, but this bug can be closed.

Comment 7 Dan Kenigsberg 2013-03-06 07:57:09 UTC
Itamar, I recall that we tried to avoid that, but I do not see a way around pushing updated vdsm-bootstrap-4.10.2-1.6 into rhev-m-3.1.z channel, and requesting customers to install it before they try to add new rhel-6.4 hosts.

Comment 8 Barak 2013-03-06 10:19:50 UTC
Dafna, 

If I recall correctly the above scenario was tested by you,
Can you please help to shed some light on the issue ?

Comment 11 Itamar Heim 2013-06-11 08:21:40 UTC
3.2 has been released

Comment 12 Itamar Heim 2013-06-11 08:24:24 UTC
3.2 has been released


Note You need to log in before you can comment on or make changes to this bug.