Bug 1265525

Summary: [New] - upgrading console from 3.0 to 3.1 does not work
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: rhgs-3.1CC: asrivast, divya, nlevinki, rhs-bugs, rnachimu, sabose, sankarshan, trao
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhsc-3.1.2-0.67 Doc Type: Bug Fix
Doc Text:
Previously, upgrade of rhsc-setup-plugin required a specific version of rhsc and rhsc packages could not be updated due to the version lock issue. As a consequence, upgrade from 3.0.x to 3.1.2 failed. With this fix, this package dependency issue is resolved and upgrade works as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-01 06:11:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1260783    

Description RamaKasturi 2015-09-23 07:06:40 UTC
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):
rhsc-3.0

How reproducible:
Always

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

Actual results:
rhsc-setup fails with error ***L:ERROR Internal error: cannot import name constants_access_plugin 

Expected results:
customer should be able to setup rhsc successfully.

Additional info:

Comment 2 RamaKasturi 2015-09-23 07:12:27 UTC
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.

Comment 5 Sahina Bose 2015-10-21 06:02:25 UTC
Changed the import location of constants file to rhsc_constants_access_plugin which is provided by the rhsc-setup-plugins rpm

Comment 6 Sahina Bose 2015-10-21 10:35:21 UTC
Please test upgrading from 3.0.x to 3.1.2 as well (x should be less than 3)

Comment 7 Triveni Rao 2015-10-27 09:22:28 UTC
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'
[root@dhcp35-212 yum.repos.d]# 

Steps followed:
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.

Comment 8 Triveni Rao 2015-11-09 13:01:29 UTC
i have completed the upgrade test from 3.0.x to 3.1.2 and found no issues.

Steps followed:
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

Comment 9 Ramesh N 2015-12-14 04:54:01 UTC
Doc text is not required as the bug is introduced in the intermediate build and customer won't face this issue at all.

Comment 10 Ramesh N 2015-12-14 05:20:27 UTC
(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

Comment 11 Divya 2016-01-29 10:01:09 UTC
Sahina,

Could you please review and sign-off the edited doc text.

Comment 12 Sahina Bose 2016-01-29 10:51:18 UTC
Looks good to me

Comment 14 errata-xmlrpc 2016-03-01 06:11:50 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.

https://rhn.redhat.com/errata/RHBA-2016-0310.html