Bug 1262712

Summary:	[New] - Cannot upgrade rhsc from 3.0.4 to 3.1.1
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.1	CC:	asrivast, byarlaga, nlevinki, rcyriac, rhs-bugs, sabose, sankarshan, sasundar
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhsc-3.1.0-65	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-01 06:11:46 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:

Description RamaKasturi 2015-09-14 07:39:46 UTC

Description of problem:
If user has an existing installation of 3.0.4 , upgraded to 3.1 and if he tries to upgrade it to 3.1.1 it fails with error below.

[root@dhcp37-66 ~]# rhsc-setup 
***L:ERROR Internal error: cannot import name constants_access_plugin

Doing a fresh install of 3.1 and upgrading to 3.1.1 has no issues. Upgrade goes successfully.

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.62.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Have RHSC installed on 3.0.4
2. upgrade rhsc to 3.1
3. Add the latest 3.1.1 repos
4. Run yum update rhsc-setup followed by rhsc-setup

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

Expected results:
rhsc-setup should run successfully.

Additional info:

Comment 4 RamaKasturi 2015-09-16 11:02:06 UTC

Verified and works fine with build rhsc-3.1.1-0.65.el6.noarch

Performed an upgrade from RHSC 3.0.4 to 3.1 and then to 3.1.1. Upgrade went fine and was successful.

Performed an upgrade from RHSC 3.1 to 3.1.1 and it went fine and was successful.

Marking this bug verified.

Comment 6 errata-xmlrpc 2016-03-01 06:11:46 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