Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionVitaly Kuznetsov
2013-08-09 07:44:12 UTC
Description of problem:
Subscriptions allocation is not optimal afeter renewal event (or manifest change).
Example:
1) Customer has 3 RH0103708 subscriptions (Red Hat Enterprise Linux
Server, Premium (8 sockets) (Up to 4 guests)
2) Customer has 3 physical systems, one of them is running virtual
guest. All of them are covered with subscriptions (physical systems use
RH0103708 subscriptions, virtual guest is covered by special 'inherited'
guest subscription)
3) Renewal event is happening. New manifest is being uploaded and
'refresh' is being performed.
4) Virtual system comes first and grabs subscription for physical system
(instead of special 'inherited' one for virtual guest)
5) Now one of physical systems (in worst scenario - host system for the
virtual guest) is not covered by a subscription. Only manual action like
detach from virtual, attach to physical, auto-attach virtual will help.
I believe we have a whole class of such issues. E.g. if we have
2 subscription - one RHEL 1-2 sockets and the other up to 4 sockets and
two systems with 2 and 4 sockets the system with 2 sockets can grab
4-socket subscription and 4-socket system won't be covered.
Version-Release number of selected component (if applicable):
# rpm -qa | grep -P 'katello|candlepin'
katello-glue-elasticsearch-1.4.3-5.el6sam_splice.noarch
candlepin-scl-rhino-1.7R3-1.el6_4.noarch
katello-cli-common-1.4.3-4.el6sat.noarch
katello-headpin-all-1.4.3-5.el6sam_splice.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-1.4.3-4.el6sat.noarch
signo-katello-0.0.10-2.el6sat.noarch
katello-glue-candlepin-1.4.3-5.el6sam_splice.noarch
candlepin-0.8.19-1.el6sam.noarch
candlepin-scl-runtime-1-5.el6_4.noarch
candlepin-scl-1-5.el6_4.noarch
katello-common-1.4.3-5.el6sam_splice.noarch
katello-headpin-1.4.3-5.el6sam_splice.noarch
candlepin-selinux-0.8.19-1.el6sam.noarch
candlepin-tomcat6-0.8.19-1.el6sam.noarch
katello-configure-1.4.4-2.el6sat.noarch
katello-selinux-1.4.4-2.el6sat.noarch
candlepin-scl-quartz-2.1.5-5.el6_4.noarch
katello-certs-tools-1.4.2-2.el6sat.noarch