Bug 1335193 - Updated SKU attributes are not updated when uploading a new subscription manifest.
Summary: Updated SKU attributes are not updated when uploading a new subscription mani...
Keywords:
Status: ASSIGNED
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: William Poteat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1323817
TreeView+ depends on / blocked
 
Reported: 2016-05-11 14:10 UTC by Barnaby Court
Modified: 2021-03-25 03:55 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Barnaby Court 2016-05-11 14:10:43 UTC
+++ This bug was initially created as a clone of Bug #1323817 +++

Description of problem:

Customer who is using the Red Hat Enterprise Linux Self-Supported Business Partner NFR (RH3387200), SKU with Satellite 6.1.

Recently, Platform BU changed this SKU's properties so that its VIRT_LIMIT attribute was raised from 20 to 100. The customer wants to take advantage of the new headroom provided by the SKU, and while downloading a new manifest shows the new limit, the existing pools aren't updated when it is uploaded to Satellite. See 

Version-Release number of selected component (if applicable):
candlepin-0.9.49.12-1.el7.noarch
katello-2.2.0.19-1.el7sat

How reproducible:


Steps to Reproduce:
1. Upload a manifest with a SKU with a VIRT_LIMIT of 20 (or any other integer)
2. Ensure the subscription pools show a value of 20. 
3. Update a new manifest with the name SKUs, but with an updated VIRT_LIMIT > 20 (or the original value you selected) 

Actual results:
Subscription pools are not updated with the new value. 

Expected results:
Subscription pools are updated with the new value. 

Additional info:

--- Additional comment from Barnaby Court on 2016-04-04 15:36:15 EDT ---

Additional information is on BZ 1322156 that this is blocking.


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