Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Launch few ec2 deployments. 2.stopped one ec2 deployment. 3.Try deleting the stopped ec2 deployment. UI displays: The deployment ec3 could not be deleted. see attached screenshot. Expected results: deployments with stopped instances should get deleted. Additional info: [root@hp-xw6400-01 html]# rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-5.el6.noarch rubygem-aeolus-image-0.3.0-2.el6.noarch rubygem-aeolus-cli-0.3.0-3.el6.noarch aeolus-all-0.8.0-5.el6.noarch aeolus-conductor-0.8.0-5.el6.noarch aeolus-configure-2.5.0-3.el6.noarch aeolus-conductor-daemons-0.8.0-5.el6.noarch
Created attachment 552090 [details] deployment
Aziza can you recreate and attach deltacloud and rails logs
adding to ce-sprint
removing ce-sprint-next tracker
deltacloud logs does not display anything while this action is performed. Attaching rails.log.
Created attachment 555937 [details] rails.log
patch submitted: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008188.html
Pushed to 1.0-staging: commit c6bb710493f4afa25e9cb66923f057eec179407c BZ 773277 fixed logical operator mistake
included in aeolus-conductor-0.8.0-10
Deployments with stopped instances in it gets deleted. however, the message for ex "The deployments ec2-single and ec2-one were scheduled for deletion" is displayed after the deployments are deleted.Therefore the deployment deletion process is very slow and takes lot of time to perform this action. The scheduled message should be displayed first and then deployments should be deleted. rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-3.el6.noarch aeolus-conductor-doc-0.8.0-11.el6.noarch rubygem-aeolus-cli-0.3.0-5.el6.noarch aeolus-configure-2.5.0-7.el6.noarch aeolus-conductor-daemons-0.8.0-11.el6.noarch aeolus-conductor-0.8.0-11.el6.noarch aeolus-all-0.8.0-11.el6.noarch
Created attachment 557380 [details] deployment_deletion_message
Would it be possible to open up a new ticket instead of continuing this one? I feel like the above is fundamentally different from the intended ticket purpose. I wasn't sure, but maybe someone on the QA team can verify - are BZs 770555 and 783531 duplicates of this one?
I've been poking around this a bit, a few comments: a) it doesn't seem like the deletion takes much longer than a few other pages/actions - maybe 5-10 seconds. Does it take longer for you? b) the delete action *does* seem to be put into a queue, which means that I don't think we can show the scheduling message any faster. If we do, it means that we're showing the "queue success" message *before* the actions are actually queued up, which is obviously a risk in case the queue actually fails.
Stopped instances can be deleted rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-16.el6.noarch aeolus-configure-2.5.0-11.el6.noarch aeolus-conductor-daemons-0.8.0-16.el6.noarch rubygem-aeolus-image-0.3.0-6.el6.noarch aeolus-all-0.8.0-16.el6.noarch aeolus-conductor-0.8.0-16.el6.noarch rubygem-aeolus-cli-0.3.0-7.el6.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html