Created attachment 597180 [details] Screencast showing deployment removal problem. Description of problem: With upstream Aeolus 0.10.x rpms (on F16), it's not possible to remove failed deployments. For example, with a recent setup, I have 3 wordpress deployments which failed when being started up. All three completely refuse to go away, no matter what I try to do to delete them. Screencast showing the problem (.mp4) attached. The deployment instance history and other info tabs are shown in the screencast. Version-Release number of selected component (if applicable): aeolus-all-0.10.4-1.fc16.noarch aeolus-conductor-0.10.4-1.fc16.noarch aeolus-conductor-daemons-0.10.4-1.fc16.noarch aeolus-conductor-devel-0.10.4-1.fc16.noarch aeolus-conductor-doc-0.10.4-1.fc16.noarch aeolus-configure-2.6.0-1.fc16.noarch rubygem-aeolus-cli-0.5.0-1.fc16.noarch rubygem-aeolus-image-0.5.0-1.fc16.noarch How reproducible: Every time. Steps to Reproduce: 1. Probably the easiest way to cause a failed deployment, is by manually removing a VMware image from the backend NFS storage, once it's been pushed. 2. After that, Aeolus will attempt to launch the deployment, but the instance with missing storage will be status "create_failed". It's deployment will not be removable.
a patch sent: https://fedorahosted.org/pipermail/aeolus-devel/2012-July/011266.html
pushed to master, commits: 8290aa1cfef19e54252256ea84f81120f46a6b99 94b243ac4af6b416e48528457d8bb4b5bcdc05b6
Found a case where deployments still can be killed. Screenshots attached showing the problem, the History tab for the instance in question, and the related error in the VMware screen that I think caused it. Looks like a follow up patch is needed. ;)
Created attachment 598220 [details] Screenshot showing flash message about deployment not being delete-able.
Created attachment 598221 [details] History tab for the instance that refuses to go away.
s/still can be killed/still can't be killed/
the issue described in Comment 3 is not conductor-related, it's probably dc-api bug, created new bug for it here: https://issues.apache.org/jira/browse/DTACLOUD-287
Tested 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 failed deployment by launching an instance in a rhevm realm with no hosts to start the vm. I was able to delete the deployment from the /conductor/deployments page. See the attached screenshots. Marking this BZ as 'verified'
Created attachment 615603 [details] Failed deployment listed
Created attachment 615604 [details] Failed deployement deleted
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