Description of problem: recreate: 1. create a provider 2. create a provider account 3. try to delete the provider account.. Processing Admin::ProviderAccountsController#index (for 10.11.228.65 at 2011-02-16 11:42:22) [GET] Parameters: {"action"=>"index", "controller"=>"admin/provider_accounts"} Rendering template within layouts/application Rendering admin/provider_accounts/index Completed in 687ms (View: 33, DB: 29) | 200 OK [http://10.16.120.137/deltacloud/admin/provider_accounts] Processing Admin::ProviderAccountsController#multi_destroy (for 10.11.228.65 at 2011-02-16 11:42:25) [DELETE] Parameters: {"accounts_selected"=>["1"], "__rewrite"=>{"delete"=>"Delete"}, "action"=>"multi_destroy", "controller"=>"admin/provider_accounts", "__map"=>{"delete"=>{"method"=>"DELETE", "url"=>"/deltacloud/admin/provider_accounts/multi_destroy"}}} Redirected to http://10.16.120.137/deltacloud/admin/provider_accounts Completed in 572ms (DB: 44) | 302 Found [http://10.16.120.137/deltacloud/admin/provider_accounts/multi_destroy] Processing Admin::ProviderAccountsController#index (for 10.11.228.65 at 2011-02-16 11:42:26) [GET] Parameters: {"action"=>"index", "controller"=>"admin/provider_accounts"} Rendering template within layouts/application Rendering admin/provider_accounts/index Completed in 306ms (View: 24, DB: 25) | 200 OK [http://10.16.120.137/deltacloud/admin/provider_accounts]
Testing this more now.. This may just be due to running instances.. In which case the proper warning message should be issued.
Even with stopped instances, you cannot delete the provider account and the user gets zero feedback.
adding to the ce-beta blocking tracker
this is a blocker for the automation
Posted a fix to the aeolus-devel mailing list: https://fedorahosted.org/pipermail/aeolus-devel/2011-March/000624.html With the patch you should be able to delete the account if all its instances are stopped. And it displays an error message otherwise.
The missing error message issue is fixed in the `next` branch. However, the only way to delete a provider account is when there are no instances associated with it. The reason is that some instances could be started again after they're stopped. To resolve the confusion, 2 things should be done: 1) making it easier/possible to delete instances 2) distinguish between stopped instances that are truly dead (stateless) and those that can be started again (stateful). Then we can delete an account that has no restartable instances associated with it. I think these should be made into separate issues, though.
Just an FYI for #1 in comment 6, bug 683986 tracks the issue were selecting multiple instances only stops one. An idea for easier with the assumption of a fix for bug 683986, perhaps have the delete recognize running instances, ask for a acknowledgement like a checkbox, and do both actions for the user in one delete action.
Providers can be deleted now.
1) Create a provider. 2) Create a provider account. 3) Launch Instance. With running instance : Account ssachdev was not deleted. There are instances associated with it. With stopped instance also :Account ssachdev was not deleted. There are instances associated with it. Provider account cannot be deleted.
moving to on_qa for review
Verified : 1) with running instances , account cannot be deleted with this validation message . Errors * Account ssachdev_west was not deleted. There are instances associated with it. 2) Without running instance , account can be deleted.
release pending...
perm close
closing out old bugs