Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Create a user with only "global profile user" 2.Login to conductor as "Global profile user" 3.Go to Content --> Hardware 4. Select any hwp and click delete Actual results: Displayed the error msg "rehana_hmp1 could not be deleted " Expected results: This should be changed to "“Insufficient privileges to do the operation or so” Additional info: rpm -qa | grep aeolus aeolus-conductor-0.8.3-1.el6.noarch aeolus-conductor-daemons-0.8.3-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-all-0.8.3-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.3-1.el6.noarch
patch on list: [PATCH conductor] bug 807752: appropriate error message for permission denied on HWP deletion
commit 95d037bffb0a0c394064a4d641afe3e0742fc796 Author: Scott Seago <sseago> Date: Wed Sep 5 14:26:18 2012 -0400 bug 807752: appropriate error message for permission denied on HWP deletion https://bugzilla.redhat.com/show_bug.cgi?id=807752 Signed-off-by: Jason Guiditta <jguiditt> On 1.1 at b191d199cd9a886f7b68c9493991ba28d6b062dc
in build aeolus-conductor-0.13.3-1.el6cf
Testing rpms: >> rpm -qa |grep aeolus aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch - Created a user with only Global HWP User Permissions - Logged in to Conductor as that user - Navigated to Administer-> Content -> Hardware - Tried to delete the mock HWP set up - Received the following error: Errors Insufficient permissions to delete hardware profile mockX86_64LARGE See the attached screenshot Marking this BZ as 'verified'.
Created attachment 615106 [details] Insufficient permissions error
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. http://rhn.redhat.com/errata/RHEA-2012-1516.html