Bug 719962

Summary: Unable to delete a deployment with instances that have STATE_ERROR
Product: [Retired] CloudForms Cloud Engine Reporter: Michael Solberg <msolberg>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: akarol, dajohnso, deltacloud-maint, dgao, ssachdev
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: 2011-07-08 18:28:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Solberg 2011-07-08 14:30:39 UTC 
Description of problem:

I've ended up with a couple of instances in STATE_ERROR that I couldn't delete from the web UI.  The current test for whether or not an instance (and thus the deployment) is destroyable is this:

(state == STATE_CREATE_FAILED) or (state == STATE_STOPPED and not restartable?)

Is there any reason that we shouldn't include instances in the STATE_ERROR state?

Version-Release number of selected component (if applicable):
aeolus-conductor-0.3.0-0.el6.20110707201945gitc26c54e.noarch

How reproducible:
100%

Steps to Reproduce:
1. Try to delete a deployment which has instances in the STATE_ERROR state.
  
Actual results:
Error.

Expected results:
Deployment is deleted.
Comment 1 wes hayutin 2011-07-08 18:28:48 UTC 

*** This bug has been marked as a duplicate of bug 698269 ***
Comment 2 wes hayutin 2011-12-08 14:06:27 UTC 
perm close