Red Hat Bugzilla – Bug 701767
Suborg allocated only flex entitlements cannot access software channels
Last modified: 2012-03-08 04:06:43 EST
Description of problem:
On a 5.4 satellite, if you create a suborganization and only give it flex entitlements, satellite users (even org admins) cannot:
- access the channels overview in the webUI
Channels tab shows "No channels found."
- create Activation Keys that specifies a base channel
webUI shows "We're sorry, but the channel could not be found." and tomcat logs shows:
2011-04-28 09:29:05,936 [TP-Processor3] WARN com.redhat.rhn.common.errors.LookupExceptionHandler - User 125 does not have access to channel 121 or the channel does not exist
Apr 28, 2011 5:30:07 PM org.apache.coyote.http11.Http11BaseProtocol pause
- register clients
fails with Error Class Code: 71
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. As sat admin, create suborg in 5.4 webUI
2. Allocate base entitlements and only flex software channel entitlements
3. As new suborg's admin, try to access any channel from the Channel tab, create an Activation Key, or register a client
Failure; acts like the user does not have permissions to access the channel.
fixed in upstream ... in spacewalk-schema package ...
for QA: please, try to test several actions, not just those three listed in the #Description
fixing sha1 of PG upgrade file ...
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
When only flex entitlements (and no regular) were assigned to an organization, the organization rights were not properly recognized.
If an organization has only flex entitlements assigned, access channels rights are properly recognized.
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.