Bug 839178 - Global role grants tab not working "invalid permission object type " error displayed
Summary: Global role grants tab not working "invalid permission object type " error di...
Keywords:
Status: CLOSED DUPLICATE of bug 838939
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-11 07:15 UTC by pushpesh sharma
Modified: 2014-08-04 22:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-11 07:21:28 UTC
Embargoed:

Attachments (Terms of Use)
global_role_grant_err (118.27 KB, image/png)
2012-07-11 07:15 UTC, pushpesh sharma 		no flags Details
View All

Description pushpesh sharma 2012-07-11 07:15:27 UTC 
Created attachment 597474 [details]
global_role_grant_err

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.logged in as admin
2.created a user group and some user
3.navigated to "Global role grants " tab and got the "invalid permission object type " error.
 
  
Actual results:
sholud be able to grant global roles. 

Expected results:


Additional info:[root@qeblade29 ~]# rpm -qa|grep aeolus
aeolus-configure-2.7.0-0.20120709172029gite93c068.fc16.noarch
aeolus-conductor-0.11.0-0.20120709213339gitb6f79a1.fc16.noarch
aeolus-all-0.11.0-0.20120709213339gitb6f79a1.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120709213339gitb6f79a1.fc16.noarch
aeolus-conductor-devel-0.11.0-0.20120709213339gitb6f79a1.fc16.noarch
rubygem-aeolus-cli-0.6.0-0.20120710182001gite2a391a.fc16.noarch
aeolus-conductor-doc-0.11.0-0.20120709213339gitb6f79a1.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120710181941git05a815a.fc16.noarch
Comment 1 pushpesh sharma 2012-07-11 07:21:28 UTC 

*** This bug has been marked as a duplicate of bug 838939 ***
Note You need to log in before you can comment on or make changes to this bug.