Bug 784499 - Deleting running deployments says "The deployment could not be deleted",but actually gets deleted.
Summary: Deleting running deployments says "The deployment could not be deleted",but a...
Keywords:
Status: CLOSED CURRENTRELEASE
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: Shveta
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 07:24 UTC by Aziza Karol
Modified: 2012-08-30 17:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:15:37 UTC


Attachments (Terms of Use)
deployment msg (235.60 KB, image/png)
2012-01-25 07:25 UTC, Aziza Karol
no flags Details
deployment deleted (234.22 KB, image/png)
2012-01-25 07:26 UTC, Aziza Karol
no flags Details
deleting running deployment (233.60 KB, image/png)
2012-02-23 07:56 UTC, Shveta
no flags Details

Description Aziza Karol 2012-01-25 07:24:04 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.launch few ec2 deployments.
2.try deleting a deployment which has a state as "running".

In UI,it displays "The deployment ec2-1isnt could not be deleted",but actually it gets deleted. see attached screenshot.


deltacloud-core  log:
thin server (localhost:3002) [deltacloud-mock][3507]: 127.0.0.1 - - [25/Jan/2012 02:15:54] "GET /api/instances/i-f05b22c0 HTTP/1.1" 502 222 1.2503
New Aws::Ec2 using per_thread-connection mode


Expected results:
Deployments in running state should be allowed to delete.


Additional info:
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

Comment 1 Aziza Karol 2012-01-25 07:25:27 UTC
Created attachment 557386 [details]
deployment msg

Comment 2 Aziza Karol 2012-01-25 07:26:12 UTC
Created attachment 557387 [details]
deployment deleted

Comment 3 Tzu-Mainn Chen 2012-01-31 22:20:11 UTC
Patch created:

https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008523.html

Comment 4 Tzu-Mainn Chen 2012-02-03 15:10:35 UTC
Email with corrected BZ number:

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008613.html

Comment 5 Tzu-Mainn Chen 2012-02-03 21:04:39 UTC
Pushed to 1.0-staging:

commit d31f56e55ab0e30a06c4d43dd9f014f9fcecd521
BZ 784499 added check to ensure task exists before saving

Comment 6 Shveta 2012-02-13 16:09:35 UTC
Deleting running Applications gives proxy error .
Aeolus-conductor service gets stopped.

https://bugzilla.redhat.com/show_bug.cgi?id=786432

Comment 7 Steve Linabery 2012-02-14 18:16:20 UTC
337a3e0 in aeolus-conductor-0.8.0-27

Comment 8 Shveta 2012-02-23 07:56:40 UTC
Created attachment 565220 [details]
deleting running deployment

Running deployments gets deleted with proper message

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


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