Bug 1323817 - 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: 0.9.54
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: William Poteat
QA Contact:
URL:
Whiteboard:
Depends On: 1335193
Blocks: 1322156
TreeView+ depends on / blocked
 
Reported: 2016-04-04 19:35 UTC by Barnaby Court
Modified: 2021-03-25 03:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1335193 (view as bug list)
Environment:
Last Closed:


Attachments (Terms of Use)

Description Barnaby Court 2016-04-04 19:35:27 UTC
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:

Comment 1 Barnaby Court 2016-04-04 19:36:15 UTC
Additional information is on BZ 1322156 that this is blocking.

Comment 2 Barnaby Court 2018-02-05 16:10:43 UTC
Changing target release to unset as this has been moved to backlog downstream.


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