Bug 722977 - virt_only pools are not removed from an owner if the physical pool no longer has a valid virt_limit
virt_only pools are not removed from an owner if the physical pool no longer ...
Status: CLOSED DUPLICATE of bug 887287
Product: Candlepin
Classification: Community
Component: candlepin (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Devan Goodwin
John Sefler
: Triaged
Depends On:
Blocks: rhsm-rhel65 rhsm-rhel70
  Show dependency treegraph
Reported: 2011-07-18 12:51 EDT by Andrew Edwards
Modified: 2016-04-18 02:00 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-03-26 10:47:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Edwards 2011-07-18 12:51:49 EDT
Description of problem:
virt_only pools are not removed from an owner if the physical pool no longer has a valid virt_limit

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

How reproducible:

Steps to Reproduce:
1. add a pool to an owner with a virt_limit of 4
2. refreshPools on the owner
3. verify that virt_only pool is created
4. modify the original pool (created in step 1) such that its virt_limit is 0.
5. refreshPools on the owner
Actual results:
The virt_only pool created by candlepin will change it's expected quantity to 0 but still exist.

Expected results:
the virt_only pool created by candlepin is removed.

Additional info:
Comment 1 Devan Goodwin 2011-12-16 14:31:17 EST
So if the refresh pools routine detects that the quantity has changed on the bonus pool, and the new virt limit is set to 0, we assume the bonus pool needs to be cleaned up and wipe it out. 

There is a very big caveat here, you cannot later set the virt limit back to something on the subscription, and refresh to get the bonus pool back. The bonus pool is for all intents and purposes permanently gone and will not be recreated unless you wipe out the physical pool as well. (using the delete pool routine)

I am also tempted to propose that we don't try to do this automatically, instead if this happens we stop setting virt_limit attribute on the subscription, and go manually delete the virt bonus pool.

Comment 2 Devan Goodwin 2012-01-10 07:32:08 EST
Andrew: are we set to just manually delete the pool when this happens? If so I will close this issue.
Comment 3 Andrew Edwards 2012-01-16 09:00:14 EST

After speaking with Amanda on this issue, we'd like for this to happen automatically. We do not control product changes and may not know when the virt limit attribute has been removed from a product.
Comment 4 Devan Goodwin 2013-03-26 10:47:33 EDT

*** This bug has been marked as a duplicate of bug 887287 ***

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