Bug 711294 - RFE : Remove failed option on instances should remove the erroneous instances not just stop them.
Summary: RFE : Remove failed option on instances should remove the erroneous instances...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
Assignee: Tomas Sedovic
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 06:24 UTC by Shveta
Modified: 2012-01-26 12:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-08 13:47:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Shveta 2011-06-07 06:24:33 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Select any  instance in "Error" state 
2. click on remove failed
3. Instance is stopped , it should be removed from the UI rather
we are not able to create another instance of the same name.
  
Actual results:


Expected results:


Additional info:

Comment 1 wes hayutin 2011-06-23 13:32:06 UTC
any idea what the plan is for this..

Comment 2 Tomas Sedovic 2011-06-30 11:47:14 UTC
So the latest on this is that we won't allow deleting instances directly at all.

We'll UI for deleting deployables. And for the time being, we'll only allow to delete whose instances are either in create_failed or stopped state.

Comment 3 wes hayutin 2011-06-30 12:52:42 UTC
k.. so just repeating to make sure I understand..

A user *can* delete a deployable

A user *can* delete a instance in *failed* or *stopped* state

Also just making sure...
In a deployable w/ more than one instance... say three instances..
One instance gets "create_failed" or is stopped for other reasons, but the other two instances in the deployable are running.

Can a user delete the one bad instance in a deployable w/ three total?

Comment 4 Tomas Sedovic 2011-06-30 13:59:54 UTC
I assume you mean "deployment" not "deployable" -- deployable is the XML definition of a deployment. Deployment is the thing running in the cloud that consists of one or more instances.

User *cannot* delete instances individually. Only deployments can be deleted.

Deleting a deployment removes all instances that belong to it, too.

If any of the deployment's instances are running, the user cannot delete the deployment. However, they can stop all the instances (or stop the deployment itself -- that stops all of its instances, too) and then delete the deployment.

I've just sent a patch implementing this to the mailing list:

https://fedorahosted.org/pipermail/aeolus-devel/2011-June/002783.html

Comment 5 Tomas Sedovic 2011-07-01 11:27:08 UTC
Pushed into next: db176192f8e02a4ba345e78de947abfff1b5021a

Comment 6 Aziza Karol 2011-07-07 09:56:17 UTC
verified:
Individual instances cannot be deleted.

Only deployments can be deleted.
conditions:
Deployment is not deleted if instances are running.
if instances are failed or stopped then it can be deleted.
Also when deployment is stopped itself which intern stops all instances, then it can be deleted.

[root@dell-pe860-01 ~]# rpm -qa  | grep aeolus
aeolus-configure-2.0.1-0.el6.20110706084705git542b456.noarch
aeolus-conductor-0.3.0-0.el6.20110706142422git0ebf7d1.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110706142422git0ebf7d1.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110706142422git0ebf7d1.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110706142422git0ebf7d1.noarch
aeolus-all-0.3.0-0.el6.20110706142422git0ebf7d1.noarch

Comment 7 wes hayutin 2011-07-08 13:48:24 UTC
removing verified bugs from tracker

Comment 8 wes hayutin 2011-08-01 19:53:36 UTC
release pending...

Comment 9 wes hayutin 2011-08-01 19:55:44 UTC
release pending...

Comment 11 wes hayutin 2011-12-08 13:47:43 UTC
perm close


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