Description of problem: this bug is raised from https://bugzilla.redhat.com/show_bug.cgi?id=800849 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Login to conductor 2.launch instance on vsphere using a deleted image (pushed a image to vsphere, deleted the image from the vsphere ui, and deploy a blueprint pointed at this image which no longer existed in vsphere) Actual results: Observed that the application status was set to "stopped" Expected results: proper states should be displayed. Additional info: rpm -qa | grep aeolus aeolus-conductor-0.8.13-1.el6_2.noarch aeolus-configure-2.5.3-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-all-0.8.13-1.el6_2.noarch aeolus-conductor-doc-0.8.13-1.el6_2.noarch aeolus-conductor-daemons-0.8.13-1.el6_2.noarch
We need to determine what the proper state of a "create-failed" application is. "Stopped" might actually be OK. Putting needinfo on PM.
related to bug 843079
I wasn't able to reproduce this one: Conductor reported the status of a deployment with create_failed instances as failed Could you please check if this bug still exists in master?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days