Created attachment 965713 [details] snapshot Description of problem: Version-Release number of selected component (if applicable): 100% How reproducible: 5.2.5.3.20140811145418_a290c21 Steps to Reproduce: 1.Navigate to configure->configuration->Access control->Roles 2.check the product feature for User_limited_self_service,user_self_service and vm_user roles 3. Actual results: All the roles does not have access to cloud instances.see attached screenshot. Expected results: User with the above roles should also have access to cloud instances Additional info:
*** Bug 1186816 has been marked as a duplicate of this bug. ***
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/fe8dbc60c08e96702d4337c29f6722eb95770020 commit fe8dbc60c08e96702d4337c29f6722eb95770020 Author: Jozef Zigmund <jzigmund> AuthorDate: Wed Mar 4 15:14:13 2015 +0100 Commit: Jozef Zigmund <jzigmund> CommitDate: Mon Apr 20 19:11:28 2015 +0200 miq_user_role: Sort product feature indetifiers for some EvmRoles (user_limited_self_service, user_self_service, vm_user) https://bugzilla.redhat.com/show_bug.cgi?id=1171589 vmdb/db/fixtures/miq_user_roles.yml | 71 +++++++++++++++++++------------------ 1 file changed, 37 insertions(+), 34 deletions(-)
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/8866bd058c48f834019684d39b3f5776e7712542 commit 8866bd058c48f834019684d39b3f5776e7712542 Author: Jozef Zigmund <jzigmund> AuthorDate: Wed Mar 4 15:18:39 2015 +0100 Commit: Jozef Zigmund <jzigmund> CommitDate: Mon Apr 20 19:11:28 2015 +0200 miq_user_role: Added product feature identifier 'vm_cloud_explorer' to some EvmRoles (user_limited_self_service, user_self_service, vm_user) https://bugzilla.redhat.com/show_bug.cgi?id=1171589 vmdb/db/fixtures/miq_user_roles.yml | 3 +++ 1 file changed, 3 insertions(+)
User_limited_self_service/user_self_service/vm_user roles have access to cloud instances feature. Verified: 5.4.0.0.24.20150427192818_1fd9e49
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. https://rhn.redhat.com/errata/RHBA-2015-1100.html