Bug 767648 - Success message is displayed even if a provider deletion fails
Summary: Success message is displayed even if a provider deletion fails
Keywords:
Status: CLOSED DUPLICATE of bug 783096
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Maros Zatko
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: ce-sprint
TreeView+ depends on / blocked
 
Reported: 2011-12-14 15:38 UTC by Jan Provaznik
Modified: 2012-01-24 17:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-24 17:45:47 UTC

Attachments (Terms of Use)
del_prov (232.33 KB, image/png)
2012-01-10 11:51 UTC, Shveta 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 783195 0 unspecified CLOSED lib/addressable/uri.rb:2148: [BUG] Segmentation fault 2021-02-22 00:41:40 UTC

Internal Links: 783195

Description Jan Provaznik 2011-12-14 15:38:30 UTC 
Description of problem:
If a provider can't be deleted for some reason, 

Steps to Reproduce:
1. go to the providers page
2. create a provider and launch an instance for this provider
3. delete the provider
  
Actual results:
message "provider was deleted" is displayed but the provider wasn't actually removed

Expected results:
display message why the deletion failed
Comment 1 Jan Provaznik 2011-12-14 15:41:44 UTC 
quick grep of all controllers says that we don't check a result of destroy on many other places, which is bug too
Comment 2 Tomas Hrcka 2012-01-03 12:11:18 UTC 
fixed in git commit 1853d01251e0899f60f7ae744ccd5b12e3851844
Comment 3 Shveta 2012-01-10 11:47:50 UTC 
we get an error message that :

"Provider was not deleted, because of errors basethere are instances for cloud
account 'ssachdev': ec2_1_east/frontend "

The message needs to be further corrected.

===========================================================
rpm -qa|grep aeolus
aeolus-configure-2.6.0-0.20120105171403gitf0043e8.el6.noarch
aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-arel-2.0.10-0.aeolus.el6.noarch
rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch
rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.el6.noarch
aeolus-conductor-0.9.0-0.20120105223209git5e068fe.el6.noarch
aeolus-all-0.9.0-0.20120105223209git5e068fe.el6.noarch
rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.el6.noarch
aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.el6.noarch
Comment 4 Shveta 2012-01-10 11:51:47 UTC 
Created attachment 551820 [details]
del_prov
Comment 5 wes hayutin 2012-01-12 16:51:15 UTC 
adding to sprint tracker
Comment 6 Mike Orazi 2012-01-19 21:48:27 UTC 
Added a See Also: to another ruby gc bug.
Comment 7 Maros Zatko 2012-01-23 12:05:31 UTC 
This is fixed in https://bugzilla.redhat.com/show_bug.cgi?id=783096

(In reply to comment #3)
> we get an error message that :
> 
> "Provider was not deleted, because of errors basethere are instances for cloud
> account 'ssachdev': ec2_1_east/frontend "
> 
> The message needs to be further corrected.
> 
> ===========================================================
> rpm -qa|grep aeolus
> aeolus-configure-2.6.0-0.20120105171403gitf0043e8.el6.noarch
> aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.el6.noarch
> rubygem-arel-2.0.10-0.aeolus.el6.noarch
> rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch
> rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch
> rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.el6.noarch
> aeolus-conductor-0.9.0-0.20120105223209git5e068fe.el6.noarch
> aeolus-all-0.9.0-0.20120105223209git5e068fe.el6.noarch
> rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.el6.noarch
> aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.el6.noarch
Comment 8 wes hayutin 2012-01-24 17:45:47 UTC 

*** This bug has been marked as a duplicate of bug 783096 ***
Note You need to log in before you can comment on or make changes to this bug.