Bug 71181 - RFE: Revised Entitlement Policy
RFE: Revised Entitlement Policy
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Matt Jamison
: 75925 (view as bug list)
Depends On: 79095
Blocks: 74703 76112 77958
  Show dependency treegraph
Reported: 2002-08-09 13:01 EDT by Brian Faustyn
Modified: 2008-05-01 11:38 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-13 14:21:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Faustyn 2002-08-09 13:01:01 EDT
Description of Problem:
Activation Keys do not assign a system to a base channel.

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

How Reproducible:

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Comment 1 Greg DeKoenigsberg 2002-10-22 13:31:21 EDT
Renaming this to "Revised Entitlement Policy" so that it can incorporate the
entire new entitlement policy.

The basic premise for the new policy: if a customer specifies an activation key,
use it to the best of your ability, or die with error.  If no activation key is
specified, entitle them automatically wherever possible -- unless they've
specifically chosen a preference on the website that says "don't automatically

This means that, in addition to the changes in the registration code, the
following new functionality is required:

* When a new org is created, add a default org-level preference for
"auto-entitle" and set it to "yes".
* Place a new org-level preference on the web site for "auto-entitle".

The full policy for this feature is detailed in CVS: 
Comment 2 Greg DeKoenigsberg 2002-10-22 13:54:39 EDT
*** Bug 75925 has been marked as a duplicate of this bug. ***
Comment 3 Mihai Ibanescu 2002-11-05 13:53:01 EST
Should be on my plate.
Comment 4 Mihai Ibanescu 2002-11-22 10:44:29 EST
Implemented, in devel.

Test plan:
Comprehensive QA of the registration code is required. Additionally, one should
explore a couple of different scenarios. The full algorithm is described in
cvs/rhn/docs/EntitlementPolicy.txt - try to break the code with cornercases.

- token entitlement
  - enterprise entitlements available
  - enterprise entitlements exhausted, basic entitlements available [should fail]
  - no entitlements available [should fail]
  - token with no base channel specified - should follow redhat-release
  - base channel specified in the entitlement token, different than what 
    redhat-release would entitle - should follow the token's
  - base channel and subchannels specified - subchannels are correctly 
  - subchannels without an available entitlement specified (like, say, the proxy  
    channel): should not subscribe to these channels
  - server groups present in the token (not sure if it's implemented web-side)

- non-token entitlement
  - fresh system to a fresh user - should be entitled to basic
  - create fresh user, grant enterprise slots to that user's org, subscribe 
    systems. Should receive enterprise entitlements first, followed by the free
    basic entitlement, then no entitlement.

Maybe find more test cases...
Comment 5 Greg DeKoenigsberg 2002-12-11 09:10:37 EST
Setting to high/high and reassigning to jkt.
Comment 6 Josef Komenda 2002-12-13 11:30:05 EST
Testing Activation keys for another bug, so I'll add my results here. 

All testing was looking good until I tried to creat a custom child channel and
select the custom base channel and the child channel:

Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 294, in ?
  File "/usr/sbin/rhnreg_ks", line 267, in main
    profileName = profilename)
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 274, in registerSystem
    raise up2dateErrors.CommunicationError(f.faultString)
up2dateErrors.CommunicationError: Error communicating with server. The message was:
While running 'registration.new_system': caught
exceptions.TypeError : unexpected keyword argument: commit
Comment 7 Mihai Ibanescu 2002-12-13 11:38:11 EST
Fixed and deployed in devel.
Comment 8 Josef Komenda 2002-12-13 11:42:58 EST
Activation keys seem to work properly in all cases. Still need to test new
account  registration without tokens.
Comment 9 Josef Komenda 2002-12-13 14:21:31 EST
Non-token stuff works as advertised on dev, closing.

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