Bug 1020409 - Product deletion refreshes pools for entire org
Summary: Product deletion refreshes pools for entire org
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 15:37 UTC by Justin Sherrill
Modified: 2017-02-13 03:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-13 03:27:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Justin Sherrill 2013-10-17 15:37:16 UTC
Description of problem:

Currently when you delete a product it calls Resources::Candlepin::Subscription.refresh_for_owner() which refreshes the pools for a systems within the organization.

This is extremely slow when you have lots of systems


How reproducible:
always

Steps to Reproduce:
1.  Register ~200 systems
2.  Create a product, do not create a repo, do not assign systems to it
3.  Delete the product

Actual results:
Very slow (~60 seconds)


Expected results:
Should be fast

Additional info:
As far as I know there is no reason to refresh the pools for all systems in the org

Comment 1 Justin Sherrill 2013-10-17 15:38:41 UTC
Ideally this shouldn't block the request regardless as well, it should occur in the background.

Comment 2 RHEL Program Management 2013-10-17 15:56:03 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 6 Justin Sherrill 2017-02-13 03:27:47 UTC
Looks like this was removed from Product delete some where before 6.2 but was still being called during product create.  It was removed as part of the candlepin 2.0 work.  I'll go ahead and close this as I don't know that this is affecting customers.


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