Hide Forgot
Description of problem: I noticed that when I delete a template, the action fails to clean up the built template contained in the warehouse. We probably need to clean these up to because we run the risk of filling up the file system with orphaned data. Version-Release number of selected component (if applicable): [root@dell-pe1950-01 log]# rpm -qa | grep aeolus aeolus-configure-2.0.0-5.fc14.20110401173241git4d62feb.noarch aeolus-conductor-daemons-0.0.3-0.fc14.20110401225256git6800ed8.x86_64 aeolus-conductor-0.0.3-0.fc14.20110401225256git6800ed8.x86_64 aeolus-conductor-doc-0.0.3-0.fc14.20110401225256git6800ed8.x86_64
We should think through the implications of this. What if the image is currently running in some backend? What if the template was generated from kalpana? What if there are multiple people using the UI, and somebody else has it open? I'm not saying we shouldn't clean up images, or even that we shouldn't delete templates. But we should think through the implications of these kinds of operations.
As there is no UI around templates in the conductor any more, is this even still a valid BZ?
Dave, can you retest this just using the aeolus-image command. Thanks
making sure all the bugs are at the right version for future queries
please see my question from september, otherwise, lets just close this out
This one is good to go now with both aeolus-image command as well as the ui built around component outlines using aeolus-conductor-0.8.0-19.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-0583.html