Bug 797172

Summary: Instances should show state "create_failed" when failed to launch and such deployments should be allowed to delete
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <ssachdev>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, brad, dajohnso, deltacloud-maint, dgao, ssachdev, whayutin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-27 19:10:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
new state none

Description Shveta 2012-02-24 12:57:50 UTC 
Created attachment 565595 [details]
new state

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. In reference to bug https://bugzilla.redhat.com/show_bug.cgi?id=785094
2. create a deployment with 25 assemblies and launched with a realm not mapped to 
any provider
3. Long flash error was displayed but instances launched and shows "new" state
4. deployment shows Pending state.
5. when trying to delete that deployment , it can't be deleted.
  
Actual results:


Expected results:


Additional info:
rpm -qa|grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
Comment 1 Martin Kočí 2012-02-24 13:21:01 UTC 
Correct me if I'm wrong, but shouldn't be this opened against aeolus-conductor then imagefactory ?
Comment 2 wes hayutin 2012-02-27 19:10:50 UTC 

*** This bug has been marked as a duplicate of bug 796528 ***