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.

Description of problem:
In subscription-manager-gui, "Quantity" default value changed to 0 from 1 after Attach the Subscripion 

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

RHEL7.0-everything-20131127.1-x86_64
subscription-manager-gui-1.10.6-1.el7
subscription-manager-firstboot-1.10.6-1.el7
subscription-manager-1.10.6-1.el7
python-rhsm-1.10.6-1.el7

How reproducible:
always

Steps to Reproduce:
1.Register the system and open subscription-manager-gui
2.Go to "All Available Subscriptions" tab and press "Update" button
3.Select a Multi-entitlement subscription notice that the "Quantity"'s default value is "1", then press "Attach" button.
4.After the attachment, take a look at the Quantity value

Actual results:
The default value become to "0" not "1". please look at the attachment.

Expected results:
The default value should still be "1".

Additional info:

Created attachment 830126 [details]
screen shot when error happens

If the subscription is stackable, and the stack is already completely compliant, the suggested quantity should be zero, this seems correct.  If you click upon the quantity, it should become 1, because you cannot bind quantity 0.

This behavior occurs because separate subscriptions can stack together, and affect the quantity required of other pools.