Bug 1130669 - Content Dashboard: Admin user told they have no access to any organizations
Summary: Content Dashboard: Admin user told they have no access to any organizations
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Dashboard
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-15 21:48 UTC by Corey Welton
Modified: 2015-12-03 16:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-03 15:23:36 UTC


Attachments (Terms of Use)

Description Corey Welton 2014-08-15 21:48:20 UTC
Description of problem:
when admin user is logged into content dashboard, they're told they have no access to any organizations and that they need admin to grant them access to organizations...?

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

Satellite-6.0.4-RHEL-6-20140813.2

How reproducible:


Steps to Reproduce:
1.  Login as 'admin' user
2.  Assure you have an org selected and go to Monitor > Content Dashboard
3.  View results

Actual results:
You do not currently have access to any organizations.  Please contact an administrator to get permission to access an organization.

Expected results:
This message should not be there.

Additional info:

Comment 2 Bryan Kearney 2014-09-26 19:06:41 UTC
I can not reproduce this. Are you still seeing it?

Comment 3 Craig Ison 2015-02-11 14:52:49 UTC
Same issue for me
Red Hat Satellite Version 6.0.4

Comment 8 Brad Buckingham 2015-09-03 15:23:36 UTC
Changes have been made in the Katello upstream to merge the Content Dashboard widgets in to Monitor -> Dashboard.  Due to the nature of those changes, this issue will no longer exist once merged downstream.  This should occur with Satellite 6.2.  Based on discussion with QE, we will close this bug.


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