Bug 812740
| Summary: | Unable to delete the images under a deleted cloud | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> | ||||
| Component: | aeolus-conductor | Assignee: | Jan Provaznik <jprovazn> | ||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.0.0 | CC: | akarol, asettle, athomas, deltacloud-maint, dmacpher, redakkan, slinaber, ssachdev | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Images within a provider account or cloud were left unassigned if the cloud or provider account was deleted. This update adds a warning message when attempting to delete a cloud with images.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-04 15:03:43 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
There are more options how to fix this: 1) don't allow delete provider accounts and providers which have built/pushed images and dysplay warning that these images should be deleted first 2) auto-destroy images when associated provider account is deleted 3) don't delete images when associated provider account is deleted, but show them on image build page and allow to delete them I would suggest option 1) - it's easy to implement and quite clean. Option 1 looks good for the 1.1 release. pushed in master, commit: 2628b0019825eae76439e05e1b000015f50b7b13 pushed in 1.1, commit: 6981c543cadcba94776e13589c6caa80fc794ddc patch in 1.1 was not cherry-picked from master but pushed directly because patch in master is slightly different. in build aeolus-conductor-0.13.3-1.el6cf Now displayed warning message "There are following associated images: rhel62_rhem, imp-rhevm. Delete them first." when tried to delete a cloud with images moving to verified rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.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-1516.html |
Created attachment 577643 [details] dangling images Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Created a cloud CLoud_shv and created some images under it as non admin user 2. Next i deleted this cloud as admin. 3. images shows N/A under cloud ( fine ) but there is no way to delete such images as shown in the attached screenshot. Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.8.7-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-conductor-0.8.7-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-all-0.8.7-1.el6.noarch aeolus-conductor-daemons-0.8.7-1.el6.noarch