Red Hat Bugzilla – Bug 816194
The status of Application is marked as "stopped" when instances are in "create_failed" status
Last modified: 2016-09-20 01:03:36 EDT
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):
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)
Observed that the application status was set to "stopped"
proper states should be displayed.
rpm -qa | grep aeolus
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?