Bug 816194 - The status of Application is marked as "stopped" when instances are in "create_failed" status
Summary: The status of Application is marked as "stopped" when instances are in "creat...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-25 13:27 UTC by Rehana
Modified: 2023-09-14 01:28 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:40:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Rehana 2012-04-25 13:27:58 UTC
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

Comment 1 Hugh Brock 2012-05-07 17:54:34 UTC
We need to determine what the proper state of a "create-failed" application is. "Stopped" might actually be OK. Putting needinfo on PM.

Comment 2 Dave Johnson 2012-07-26 13:51:15 UTC
related to bug 843079

Comment 4 Imre Farkas 2013-01-18 10:47:14 UTC
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?

Comment 5 Red Hat Bugzilla 2023-09-14 01:28:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.