Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.create a non admin user. 2.In browser1 login as non admin user and try launching a deployment by clicking on new deployment.. while the nonadmin user is on the launch button .. In another browser2 login as admin and revoke the access "Global deployable user" for nonadmin user. 3.Now in browser1 click launch button. Actual results: Non admin user is still able to launch the deployments even when "Global deployable user" access is revoked. Expected results: non admin user should not be able to launch deployment. Additional info: [root@dell-pe1950-01 templates]# rpm -qa | grep aeolus rubygem-aeolus-image-0.2.0-1.el6.noarch aeolus-conductor-0.7.0-4.el6.noarch aeolus-conductor-doc-0.7.0-4.el6.noarch aeolus-configure-2.4.0-3.el6.noarch rubygem-aeolus-cli-0.2.0-3.el6.noarch aeolus-all-0.7.0-4.el6.noarch aeolus-conductor-daemons-0.7.0-4.el6.noarch
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
Patch on list here: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008141.html Commit hash: 82bdb5547174a7489ca9df77f76bbd1815a516e3
7a89a230ba064f2a36c8fd7580355d0e2b2803d2 in aeolus-conductor-0.8.0-10
Non admin user is not able to launch instance after revoking access of "global Deployable User " Message "You have insufficient privileges to perform the selected action" is displayed. verified on: rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-3.el6.noarch aeolus-conductor-doc-0.8.0-11.el6.noarch rubygem-aeolus-cli-0.3.0-5.el6.noarch aeolus-configure-2.5.0-7.el6.noarch aeolus-conductor-daemons-0.8.0-11.el6.noarch aeolus-conductor-0.8.0-11.el6.noarch aeolus-all-0.8.0-11.el6.noarch