Bug 678071
Summary: | deleting provider accounts w/ instances , needs error message. | ||
---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | wes hayutin <whayutin> |
Component: | aeolus-conductor | Assignee: | Tomas Sedovic <tsedovic> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 0.3.1 | CC: | dajohnso, deltacloud-maint, ssachdev, tsedovic |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://10.16.120.137/deltacloud/admin/provider_accounts | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 684278 |
Description
wes hayutin
2011-02-16 16:42:59 UTC
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... release pending... perm close closing out old bugs |