Bug 770815 - Deleting a catalog doesn't deletes catalog entries(under it) from db
Summary: Deleting a catalog doesn't deletes catalog entries(under it) from db
Keywords:
Status: CLOSED CURRENTRELEASE
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: Jozef Zigmund
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-29 10:23 UTC by Shveta
Modified: 2012-08-30 17:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
catalog_delete (214.17 KB, image/png)
2012-01-17 12:55 UTC, Shveta
no flags Details

Description Shveta 2011-12-29 10:23:43 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Create  a catalog (Ex: global_catalog)
2. Create catalog entry under it (catalog_entry)
3. Delete the catalog (global_catalog) , catalog entry also gets deleted from UI
4. Create the catalog again named (global_catalog)
5. create catalog entry named catalog_entry , it says names has already been taken.
Actual results:


Expected results:


Additional info:

rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch
rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch
rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch
aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch
aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch

Comment 1 wes hayutin 2012-01-12 16:51:53 UTC
adding to sprint tracker

Comment 2 Jozef Zigmund 2012-01-12 18:32:48 UTC
Bugfix is in the master with commit # a3a023ac081d1e8b98b55f93142cc7617e3d0762.

The solution in bugfix:
User shouldn't be able to delete a catalog, when its deployables have the last reference to this catalog.

If he would delete the catalog must do:
a) delete the deployable manually before deleting the catalog, or 
b) create a new catalog, add the deployable, and then delete the old catalog

Comment 3 Steve Linabery 2012-01-16 20:19:42 UTC
aeolus-conductor-0.8.0-7.el6.src.rpm

Comment 4 Shveta 2012-01-17 12:55:25 UTC
Created attachment 555758 [details]
catalog_delete

Comment 5 Shveta 2012-01-17 13:45:04 UTC
verified in 
 rpm -qa|grep aeolus
aeolus-conductor-daemons-0.8.0-7.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
aeolus-configure-2.5.0-4.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
aeolus-conductor-0.8.0-7.el6.noarch
aeolus-all-0.8.0-7.el6.noarch
aeolus-conductor-doc-0.8.0-7.el6.noarch


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