Bug 797172 - Instances should show state "create_failed" when failed to launch and such deployments should be allowed to delete
Summary: Instances should show state "create_failed" when failed to launch and such de...
Keywords:
Status: CLOSED DUPLICATE of bug 796528
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: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 12:57 UTC by Shveta
Modified: 2012-03-05 00:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-27 19:10:50 UTC

Attachments (Terms of Use)
new state (221.45 KB, image/png)
2012-02-24 12:57 UTC, Shveta 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.