Bug 806096

Summary: Read-only users cannot tell which repos are enabled from Red Hat Provider Details
Product: Red Hat Satellite Reporter: Brad Buckingham <bbuckingham>
Component: WebUIAssignee: Marek Hulan <mhulan>
Status: CLOSED UPSTREAM QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: mhulan, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 18:12:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Bottom of the RH Provider page displaying 'Enable Repositories'. The last 4 are actually enabled. none

Description Brad Buckingham 2012-03-22 21:07:41 UTC
Created attachment 572088 [details]
Bottom of the RH Provider page displaying 'Enable Repositories'.  The last 4 are actually enabled.

Description of problem:

If a user with 'read everything' role navigates to Content Management -> Content Providers -> Red Hat Content Provider, they cannot see which repositories are actually enabled.

Version-Release number of selected component (if applicable):
git master

How reproducible:
always

Steps to Reproduce:
1. import a Red Hat manifest
2. enable a few repositories
3. create a user with "Read Everything" role (e.g. readonlyuser)
4. log in as that user
5. navigate to Content Management -> Content Providers -> Red Hat Content Provider
6. click 'Enable Repositories'
  
Actual results:
If the user expands the tree of product information, there is no indication as to which repositories are actually enabled.  (I.e. all of the checkboxes have been removed).

Expected results:
The use should be able to view which repositories are enabled.  E.g. the checkboxes could still there, but disabled.

Additional info:

Comment 1 Marek Hulan 2012-12-18 14:08:29 UTC
fixed in commit 33a6d2137fd74e399c6186117443d9ab5ee268b5 PR 1279

Comment 2 Mike McCune 2013-09-19 18:12:45 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.