RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 867922 - [vdsm-bootstrap] vdsm-bootstrap of rhevm-3.0 cannot bootstrap vdsm-4.9.6 (3.1)
Summary: [vdsm-bootstrap] vdsm-bootstrap of rhevm-3.0 cannot bootstrap vdsm-4.9.6 (3.1)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Alon Bar-Lev
QA Contact: Jakub Libosvar
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 15:06 UTC by Jakub Libosvar
Modified: 2022-07-09 05:40 UTC (History)
10 users (show)

Fixed In Version: vdsm-4.9.6-40.0
Doc Type: Bug Fix
Doc Text:
Previously, changes to the internal API for VDSM 3.1 caused an error when attempting to remove a 3.0 host from Red Hat Enterprise Virtualization Manager 3.1 and re-attach it to a 3.0 Manager. This has been corrected so that hosts may be moved between 3.0 and 3.1 Managers without errors.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:13:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Bootstrap log (19.28 KB, text/x-log)
2012-10-18 15:06 UTC, Jakub Libosvar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 817898 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC
oVirt gerrit 35721 0 master MERGED api: compat: fix api breakage of 'config' and 'netinfo' used by bootstrap Never

Internal Links: 817898

Description Jakub Libosvar 2012-10-18 15:06:42 UTC 
Created attachment 629505 [details]
Bootstrap log

Description of problem:
We have a host that has been installed to 3.1 rhevm (and removed). When installing this host to 3.0, installation fails due to import error
Thu, 18 Oct 2012 15:51:26 ERROR
Traceback (most recent call last):
  File "/tmp/vds_bootstrap_0058694c-92b9-4bfb-8b18-729683d8bee2.py", line 566, in createConf
    self._makeConfig()
  File "/tmp/vds_bootstrap_0058694c-92b9-4bfb-8b18-729683d8bee2.py", line 529, in _makeConfig
    from config import config
ImportError: No module named config
Thu, 18 Oct 2012 15:51:26 DEBUG    <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed to import default values'/>
Thu, 18 Oct 2012 15:51:26 ERROR    createConf failed
Thu, 18 Oct 2012 15:51:26 DEBUG    <BSTRAP component='RHEV_INSTALL' status='FAIL'/>
Thu, 18 Oct 2012 15:51:26 DEBUG    **** End VDS Validation ****

Version-Release number of selected component (if applicable):
vdsm-4.9.6-37.0.el6_3.x86_64
vdsm-bootstrap-4.9-113.3.el6_3.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have host that was in rhevm 3.1 before
2. Install it to 3.0 rhevm
  
Actual results:
Install fails

Expected results:
Install succeeds and host is operational

Additional info:
Blocking backwards compatibility tests
Comment 1 Jakub Libosvar 2012-10-18 15:09:55 UTC 
We already had this issue some time ago: bug 817898
Comment 7 Alon Bar-Lev 2012-10-22 15:43:30 UTC 
Itamar,

This is of the legacy vdsm configuration upgrade.

I don't think we need this in 3.1...

Can we just drop it[1]?

Another option is to convert it to use the standard python ConfigParser as in other places of that code.

Alon

[1] http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vds_bootstrap/vds_bootstrap.py;h=867d6f4a764305c7476f943b89a2191e0bdce7dc;hb=HEAD#l650
Comment 8 Itamar Heim 2012-10-22 17:58:16 UTC 
Alon - what will happen if i try to install a 3.0 host on a 3.1 engine though?
Comment 9 Alon Bar-Lev 2012-10-22 18:05:33 UTC 
(In reply to comment #8)
> Alon - what will happen if i try to install a 3.0 host on a 3.1 engine
> though?

I don't understand. why will you want to do downgrade?
Comment 10 Itamar Heim 2012-10-22 18:10:39 UTC 
say i upgraded my engine, and my test cluster.
it doesn't mean i don't want to add to my production clust another host which is exactly of same configuration of all other hosts in that cluster which i tested for a long time (and is of course 3.0).

fact we have newer version of vdsm doesn't mean customers must be forced to upgrade to it for adding new hosts of same tested versions they used prior to upgrading the engine.
Comment 11 Alon Bar-Lev 2012-10-22 18:26:25 UTC 
(In reply to comment #10)
> fact we have newer version of vdsm doesn't mean customers must be forced to
> upgrade to it for adding new hosts of same tested versions they used prior
> to upgrading the engine.

Yes, but as far as I understand the upgrade of the vdsm config is for pre-3.0, no?
Comment 12 Itamar Heim 2012-10-24 03:30:58 UTC 
(In reply to comment #11)
...
> Yes, but as far as I understand the upgrade of the vdsm config is for
> pre-3.0, no?

didn't understand.
the important thing is from a 3.1 rhev-m i should be able to do a clean install of a host which is using older vdsm-4.9, rather than 4.9.6.
is this working?
Comment 13 Jakub Libosvar 2012-10-24 07:05:11 UTC 
(In reply to comment #12)
> the important thing is from a 3.1 rhev-m i should be able to do a clean
> install of a host which is using older vdsm-4.9, rather than 4.9.6.
> is this working?

We test this scenario as well and yes, host that was in 3.0 rhevm before can be installed to 3.1 rhevm.
Comment 14 Jakub Libosvar 2012-10-24 10:55:57 UTC 
Also when vdsm 4.9.6 is installed on clean 6.3, installation to 3.0 fails
Comment 15 Alon Bar-Lev 2012-10-24 11:50:57 UTC 
(In reply to comment #14)
> Also when vdsm 4.9.6 is installed on clean 6.3, installation to 3.0 fails

's/to/from/' I guess...

Jakub, Can I have access to such machine?
Comment 16 Alon Bar-Lev 2012-10-24 12:51:02 UTC 
The problem is that the older vdsm had internal API for configuration.
The bootstrap used this internal API to get variables out of vdsm module.

It used:
from config import config

Newer vdsm does not support this internal API. It should be:
from vdsm import config

Solution

Either we push a fix to vdsm-bootstrap package for rhevm-3.0 hosts. Or fix vdsm to support this old internal API.

Simplest solution is to support this internal API in vdsm.
Comment 18 Dan Kenigsberg 2012-10-24 13:29:51 UTC 
We have already agreed that it is required to install vdsm-bootstrap-4.9.6 on the Engine host before attempting to install rhev-3.1.

I do not find the exact agreement statement about it (I'm sure that Federico could have...), but I think that this bug should be closed as a dup of 804618.
Comment 19 Itamar Heim 2012-10-24 13:54:23 UTC 
(In reply to comment #18)
> We have already agreed that it is required to install vdsm-bootstrap-4.9.6
> on the Engine host before attempting to install rhev-3.1.

this is required, not an issue.

> 
> I do not find the exact agreement statement about it (I'm sure that Federico
> could have...), but I think that this bug should be closed as a dup of
> 804618.

question is what's the failed flow from all of the above:
1. adding a clean host with 4.9.6 vdsm to a rhevm-3.0.
2. adding a clean host with 4.9-113 vdsm to a rhevm-3.1.
3. other?
Comment 20 Jakub Libosvar 2012-10-24 14:05:25 UTC 
(In reply to comment #19)
> (In reply to comment #18)
> > We have already agreed that it is required to install vdsm-bootstrap-4.9.6
> > on the Engine host before attempting to install rhev-3.1.
> 
> this is required, not an issue.
> 
> > 
> > I do not find the exact agreement statement about it (I'm sure that Federico
> > could have...), but I think that this bug should be closed as a dup of
> > 804618.
> 
> question is what's the failed flow from all of the above:
> 1. adding a clean host with 4.9.6 vdsm to a rhevm-3.0.
Fails

> 2. adding a clean host with 4.9-113 vdsm to a rhevm-3.1.
Passes, even used host

> 3. other?
Basically fails when vdsm 4.9.6 is installed on host and host is added to rhevm-3.0
Comment 23 Alon Bar-Lev 2012-10-24 19:37:06 UTC 
Hi Jacob,

It will be great if you can check the following sequence.

1. Bootstrap host and fail as in previous scenario.
2. Execute the following command on that host:

echo "from vdsm import config" > /usr/share/vdsm/config.py

3. Bootstrap again.

Expected result:

Success.

Further testing:

Sanity of that vdsm.

Thanks!
Comment 24 Alon Bar-Lev 2012-10-24 19:43:29 UTC 
Barak: Flags, please.
Comment 25 Alon Bar-Lev 2012-10-25 19:58:28 UTC 
You probably need the following as well:

echo "from vdsm.netinfo import *" > /usr/share/vdsm/netinfo.py
Comment 26 Alon Bar-Lev 2012-10-25 20:07:15 UTC 
commit 80a14593eb5d66da7887fc8aa82fb594ee0d2430
Author: Alon Bar-Lev <alonbl>
Date:   Wed Oct 24 21:16:04 2012 +0200

    api: fix api breakage of 'config' and 'netinfo' used by bootstrap
    
    rhevm-3.0 depends on previous vdsm-bootstrap which uses config and
    netinfo packages.
    
    config and netinfo packages are now moved to the 'formal' vdsm api located
    at vdsm namespace.
    
    In order to allow rhevm-3.0 install vdsm-4.9.6 the legacy config and
    netinfo should be available.
    
    Change-Id: I1c854f5351980b1065a828661859332781480c3b
    Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=867922
    Signed-off-by: Alon Bar-Lev <alonbl>

https://gerrit.eng.lab.tlv.redhat.com/#/c/2852/
Comment 28 Jakub Libosvar 2012-10-29 15:23:59 UTC 
Commands in comment 23 and comment 25 fixed the problem.
Comment 29 Jakub Libosvar 2012-11-02 08:08:15 UTC 
Verified vdsm-4.9.6-40.0.el6_3.x86_64
Comment 31 errata-xmlrpc 2012-12-04 19:13:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1508.html
Note You need to log in before you can comment on or make changes to this bug.