Bug 795349 - Deleting organization while another organization has the same product fails
Summary: Deleting organization while another organization has the same product fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Garik Khachikyan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-20 10:12 UTC by Ivan Necas
Modified: 2019-09-25 21:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:27:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ivan Necas 2012-02-20 10:12:50 UTC 
Version-Release number of selected component (if applicable):
katello-0.1.238-4
candlepin-0.5.20-1

How reproducible:
Always

Steps to Reproduce:
1.Create organization
2.Import manifest
3.Create another organization
4.Import manifest for the second organization with the same product
5. Delete the second organization
  
Actual results:
deletion failed: Candlepin::Product: 400 Bad Request {"displayMessage":"Product with UUID 'ZOO' cannot be deleted while subscriptions exist."} 

Expected results:
Successfully delete organization. Another orgazniation not affected with this action.
Comment 1 Ivan Necas 2012-02-20 12:03:08 UTC 
Fixed in commit 994eee4f82539e473c22d03e69e19999dae766e9
Comment 4 Garik Khachikyan 2012-02-24 13:36:00 UTC 
# VERIFIED

impossible to reproduce due to the restriction on not being able to import the same manifest for diff. orgs.

thus: considering the issue resolved.

@Ivan: please feel free to bring the bug back to the verification if you think there is another scenario worth to try. TY.

checked on:
---

katello-0.1.300-1.el6.noarch
candlepin-0.5.22-1.el6.noarch
pulp-0.0.267-2.el6.noarch
Note You need to log in before you can comment on or make changes to this bug.