Description of problem: Currently, aeolus-cleanup cleans up all settings and restarts many of the sub components. It would be desirable to have something like aeolus-cleanup --component so it only acts on relevant settings that need fixing while leaving the ones that are working intact. For a similar example, check out the new rhevm 3.0 configuration tool, rhevm-setup, that has options for different components. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
One suggestion is that you might want to cleanup all the tools but you may wish to keep images you have created. I.e. cleanup everything except all the images I built.
Updating component: this is a component of aeolus-configure, not something related to user accounts.
making sure all the bugs are at the right version for future queries
Here is how I'm thinking of approaching this. There are two parts: (1) a command line option to cleanup but not destroy any data (2) new options to selectively cleanup specific components For two, I'll plan to implement the following options aeolus-cleanup -p iwhd aeolus-cleanup -p imagefactory aeolus-cleanup -p deltacloud aeolus-cleanup -p conductor aeolus-cleanup -p rhevm (its only action will be to unmount the rhevm export directory) There won't be a -p option for ec2 or vsphere because their configure profiles are just supersets of the above. Marcelo, let me know if this doesn't mesh with what you had in mind or if there are other scenarios to be considered. Thanks.
Changes in configure commits: 3d8c09b5d4c8a24c0b8ab26df6c3b64ef126d8d4 87b94021a70d68a1134213b293598d3a096dea60
Changes available in aeolus-configure.noarch 0:2.5.0-0.20111220094137git3d8c09b
aeolus-cleanup -p iwhd notice: /Stage[main]/Aeolus::Iwhd::Disabled/Exec[clean_iwhd]/returns: Objects deleted: 0 notice: /Stage[main]/Aeolus::Iwhd::Disabled/Exec[clean_iwhd]/returns: executed successfully notice: /Stage[main]/Aeolus::Iwhd::Disabled/Service[iwhd]/ensure: ensure changed 'running' to 'stopped' notice: /File[/var/lib/iwhd]/ensure: removed notice: /Stage[main]/Aeolus::Iwhd::Disabled/Service[mongod]/ensure: ensure changed 'running' to 'stopped' notice: Finished catalog run in 1.95 seconds [root@qe-blade-08 ~]# service iwhd status iwhd is stopped ========================================================================== aeolus-cleanup -p imagefactory notice: /Stage[main]/Aeolus::Image-factory::Disabled/Service[imagefactory]/ensure: ensure changed 'running' to 'stopped' notice: /Stage[main]/Aeolus::Image-factory::Disabled/Service[qpidd]/ensure: ensure changed 'running' to 'stopped' notice: /Stage[main]/Aeolus::Image-factory::Disabled/Exec[remove_aeolus_templates]/returns: executed successfully notice: Finished catalog run in 0.78 seconds [root@qe-blade-08 ~]# service imagefactory status imagefactory is stopped ============================================================================== aeolus-cleanup -p deltacloud notice: /Stage[main]/Aeolus::Deltacloud::Disabled/Service[deltacloud-core]/ensure: ensure changed 'running' to 'stopped' notice: Finished catalog run in 0.31 seconds [root@qe-blade-08 ~]# service deltacloud status deltacloud: unrecognized service [root@qe-blade-08 ~]# service deltacloud-core status deltacloud-core is stopped ================================================================== aeolus-cleanup -p conductor notice: /Stage[main]/Aeolus::Conductor::Disabled/Service[conductor-dbomatic]/ensure: ensure changed 'running' to 'stopped' notice: /Stage[main]/Aeolus::Conductor::Disabled/Service[aeolus-conductor]/ensure: ensure changed 'running' to 'stopped' notice: /Stage[main]/Aeolus::Conductor::Disabled/Service[httpd]/ensure: ensure changed 'running' to 'stopped' notice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: Using gem require instead of bundler notice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: executed successfully notice: /Stage[main]/Aeolus::Conductor::Disabled/Postgres::User[aeolus]/Exec[drop_aeolus_postgres_user]/returns: executed successfully notice: /File[/etc/rsyslog.d/aeolus.conf]/ensure: removed notice: /File[/var/lib/aeolus-conductor]/ensure: removed notice: Finished catalog run in 3.83 seconds [root@qe-blade-08 ~]# service aeolus-conductor status thin is stopped ========================================================================= aeolus-cleanup -p rhevm notice: Finished catalog run in 0.15 seconds verified w/ rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-25.el6.noarch aeolus-conductor-daemons-0.8.0-25.el6.noarch aeolus-configure-2.5.0-12.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch aeolus-all-0.8.0-25.el6.noarch aeolus-conductor-0.8.0-25.el6.noarch
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-0586.html