Bug 806096 - Read-only users cannot tell which repos are enabled from Red Hat Provider Details
Summary: Read-only users cannot tell which repos are enabled from Red Hat Provider Det...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Linux
unspecified
low vote
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-22 21:07 UTC by Brad Buckingham
Modified: 2019-09-26 13:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 18:12:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
Bottom of the RH Provider page displaying 'Enable Repositories'. The last 4 are actually enabled. (119.31 KB, image/png)
2012-03-22 21:07 UTC, Brad Buckingham
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.