Bug 995356 - Subscription reallocation after Renewal event is not optimal
Summary: Subscription reallocation after Renewal event is not optimal
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Carter Kozak
QA Contact: Tazim Kolhar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-09 07:44 UTC by Vitaly Kuznetsov
Modified: 2019-09-26 18:19 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-02 14:09:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vitaly 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

Comment 1 Devan Goodwin 2013-08-09 12:32:42 UTC
Moving to candlepin component.

Comment 3 Carter Kozak 2013-08-26 13:58:40 UTC
commit ea45d79bea35eb9780bba3dfa0dcc7c2ecfdbf2a
Author: ckozak <ckozak>
Date:   Thu Aug 22 16:56:10 2013 -0400

    Fix autoheal entire org

Comment 4 Carter Kozak 2013-08-26 13:59:43 UTC
That fix added logic that triggers a heal on a host machine before the guest is healed, if the host has auto-heal enabled.

Comment 5 Tom McKay 2013-08-28 18:58:25 UTC
Fixed in 0.8.23 or later

Comment 6 RHEL Program Management 2013-09-17 04:19:51 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 9 Mike McCune 2013-10-17 21:03:23 UTC
Moving this to be tested during MDP3, not critical for MDP2 success story

Comment 12 Tazim Kolhar 2014-05-22 09:35:18 UTC
please provide verification steps

Comment 13 Tazim Kolhar 2014-06-18 13:04:43 UTC
VERIFIED

Comment 14 Bryan Kearney 2014-07-02 14:09:18 UTC
This was delivered in 6.0.3, the Beta version of Satellite 6.0

Comment 15 Bryan Kearney 2014-07-02 14:09:19 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.


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