Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Try deleting hardware profile hwp1. it displays "could not deleted these hardware profile". see attached screenshot. Expected results: it should be :could not delete these hardware profile" Additional info: rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-7.el6.noarch rubygem-aeolus-image-0.3.0-2.el6.noarch rubygem-aeolus-cli-0.3.0-3.el6.noarch aeolus-all-0.8.0-7.el6.noarch aeolus-conductor-0.8.0-7.el6.noarch aeolus-configure-2.5.0-4.el6.noarch aeolus-conductor-daemons-0.8.0-7.el6.noarch
Created attachment 556009 [details] delete
Fixed in commit 559f99e4916a272f505837ec4cd743464ab7b57a
I tried deleting the default hardware profile and it got deleted successfully. Earlier, user was not allowed to delete the default hardware profile hwp1. so can the user now delete hpw1?.Is this a valid change? rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-9.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-all-0.8.0-35.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch aeolus-conductor-daemons-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch aeolus-conductor-0.8.0-35.el6.noarch
This is now fixed in upstream aeolus-configure-2.7.0-0.20120730120027gitee0ff5c.fc16.noarch
Verified On:- [root@dhcp201-113 ~]# rpm -qa|grep aeolus aeolus-conductor-doc-0.13.7-1.el6cf.noarch aeolus-all-0.13.7-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-0.13.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.7-1.el6cf.noarch [root@dhcp201-113 ~]# There is only one hwp created at the time of aeolus-configure i.e. small-x86-64 it can also be deleted.I dont consider this HWP as significant as to be called default and should be allowed to delete.
Created attachment 613853 [details] HWP delete
technical notes added.
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