Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 815099[details]
wrong suggested quantity displayed
Description of problem:
Suggested quantity displayed on GUI is not correct
Version-Release number of selected component (if applicable):
# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.8.29-1
subscription-manager: 1.9.11-1.el6
python-rhsm: 1.9.6-1.el6
How reproducible:
Always
Steps to Reproduce:
Perform the test against standalone candlepin
1. Set sockets to 20
# subscription-manager facts --list | grep socket
cpu.cpu_socket(s): 20
2. Subscribe to appropriate subscriptions so that cores are satisfied. In this case 2 of "Multi-Attribute Stackable (16 cores, 4 sockets, 8GB RAM)" provides 32 cores which satisfies cores requirement
# subscription-manager list --consumed
+-------------------------------------------+
Consumed Subscriptions
+-------------------------------------------+
Subscription Name: Multi-Attribute Stackable (16 cores, 4 sockets, 8GB RAM)
Provides: Multi-Attribute Limited Product
SKU: sock-core-ram-multiattr
Contract: 4
Account: 12331131231
Serial: 3839311457533598282
Pool ID: 8a8d01e041bc9f420141bc9fb6b606ba
Active: True
Quantity Used: 2
Service Level: Super
Service Type: Level 3
Status Details: Only covers 8 of 20 sockets.
Starts: 10/14/2013
Ends: 10/14/2014
System Type: Physical
3. From the data about we can see that 8 out of 20 sockets are covered. Go to All available subscriptions in GUI and check the suggested quantity for subscription that provides 2-sockets. In this case "Multi-Attribute Stackable (2 sockets)"
This subscriptions has two pools which provide 5 and 10 subscriptions respectively. The suggested quantity displays only 5 even thought there is a pool of 10 which can provide the necessary 6 subscriptions. (See attachment)
Actual results:
Suggested quantity displayed as 5 instead of 6
Expected results:
Suggested quantity should be 6
Additional info:
commit f07385c6fda81176e6ac4352313d9228c2b7963a
Author: ckozak <ckozak>
Date: Mon Nov 4 15:36:42 2013 -0500
1022198: Display highest suggested quantity in contract selection
We group similar pools together in the gui. Because we only
match similar pools, it doesn't matter which pool we read
attributes from. However the suggested quantity is based
upon the available quantity, which varries by pool, so
we should display the highest number.
Note: this does not fix the suggested quantity when it requires more than the maximum available quantity from either pool.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Created attachment 815099 [details] wrong suggested quantity displayed Description of problem: Suggested quantity displayed on GUI is not correct Version-Release number of selected component (if applicable): # subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.8.29-1 subscription-manager: 1.9.11-1.el6 python-rhsm: 1.9.6-1.el6 How reproducible: Always Steps to Reproduce: Perform the test against standalone candlepin 1. Set sockets to 20 # subscription-manager facts --list | grep socket cpu.cpu_socket(s): 20 2. Subscribe to appropriate subscriptions so that cores are satisfied. In this case 2 of "Multi-Attribute Stackable (16 cores, 4 sockets, 8GB RAM)" provides 32 cores which satisfies cores requirement # subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Multi-Attribute Stackable (16 cores, 4 sockets, 8GB RAM) Provides: Multi-Attribute Limited Product SKU: sock-core-ram-multiattr Contract: 4 Account: 12331131231 Serial: 3839311457533598282 Pool ID: 8a8d01e041bc9f420141bc9fb6b606ba Active: True Quantity Used: 2 Service Level: Super Service Type: Level 3 Status Details: Only covers 8 of 20 sockets. Starts: 10/14/2013 Ends: 10/14/2014 System Type: Physical 3. From the data about we can see that 8 out of 20 sockets are covered. Go to All available subscriptions in GUI and check the suggested quantity for subscription that provides 2-sockets. In this case "Multi-Attribute Stackable (2 sockets)" This subscriptions has two pools which provide 5 and 10 subscriptions respectively. The suggested quantity displays only 5 even thought there is a pool of 10 which can provide the necessary 6 subscriptions. (See attachment) Actual results: Suggested quantity displayed as 5 instead of 6 Expected results: Suggested quantity should be 6 Additional info: