Red Hat Bugzilla – Bug 1265525
[New] - upgrading console from 3.0 to 3.1 does not work
Last modified: 2016-03-01 01:11:50 EST
Description of problem:
when customer has console installations of 3.0,3.0.1,3.0.2,3.0.3 and if trying to upgrade it to 3.1 does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have installations of 3.0 / 3.0.1 / 3.0.2 /3.0.3
2. Now register to the channels which has latest packages for 3.1
3. Run yum update rhsc-setup/ rhsc-setup
rhsc-setup fails with error ***L:ERROR Internal error: cannot import name constants_access_plugin
customer should be able to setup rhsc successfully.
As a workaround copying /usr/share/ovirtengine/setup/ovirt_engine_setup/rhsc_constants_access_plugin.py as /usr/share/ovirt-engine/setup/ovirt_engine_setup/constants_access_plugin.py sloves the issue.
Changed the import location of constants file to rhsc_constants_access_plugin which is provided by the rhsc-setup-plugins rpm
Please test upgrading from 3.0.x to 3.1.2 as well (x should be less than 3)
I have completed the upgrade tests and found that after upgrade, i cannot do rhsc-setup and i see some error like this:
[root@dhcp35-212 yum.repos.d]# rhsc-setup
***L:ERROR Internal error: 'module' object has no attribute 'ENGINE_SYSCONFDIR'
1. install RHSC 3.0/3.0.1/3.0.2/3.0.3/3.0.4 on different machines.
2. upgrade to 3.1.2
3. do rhsc-setup and will see the above error.
Reproducible on all the upgrades successfully.
i have completed the upgrade test from 3.0.x to 3.1.2 and found no issues.
1. install RHSC 3.0/3.0.1/3.0.2/3.0.3/3.0.4 based on RHEL6.6 on different machines.
2. check UI and versions.
3. upgrade to 3.1.2 (rhsc-3.1.2-0.67)
4. check the UI and versions of RHSC.
Upgrades went smooth and no issues found.
This bug is verified
Doc text is not required as the bug is introduced in the intermediate build and customer won't face this issue at all.
(In reply to Ramesh N from comment #9)
> Doc text is not required as the bug is introduced in the intermediate build
> and customer won't face this issue at all.
Sorry. I was wrong. I got confused with other bug bz#1290018
Could you please review and sign-off the edited doc text.
Looks good to me
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.