Bug 450954 - Currently reprovisioning with a new base channel (via activation key) doesnt' work
Currently reprovisioning with a new base channel (via activation key) doesnt'...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration (Show other bugs)
510
All Linux
high Severity high
: ---
: ---
Assigned To: Justin Sherrill
Steve Salevan
:
: 449846 (view as bug list)
Depends On:
Blocks: 457075 496145
  Show dependency treegraph
 
Reported: 2008-06-11 17:14 EDT by Justin Sherrill
Modified: 2010-10-22 21:51 EDT (History)
6 users (show)

See Also:
Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 496145 (view as bug list)
Environment:
Last Closed: 2009-09-10 15:22:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Justin Sherrill 2008-06-11 17:14:12 EDT
In 5.1 we modified reprovisioning to allow re-activation keys and activation
keys to work together.  

Currently though, if the activation key has a different base channel, the
registration fails with a conflicting activation key error.

We need to modify the backend so that it will look at the non-reactivation key
for the base channel if they differ.
Comment 1 Clifford Perry 2008-10-08 12:11:21 EDT
*** Bug 449846 has been marked as a duplicate of this bug. ***
Comment 2 Brandon Perkins 2008-10-08 12:12:22 EDT
Bug 449846 has been marked as a duplicate of this bug.  Please verify this to be the case.  The issue still needs to be checked, but Cliff and I found no delta between the two.
Comment 4 Justin Sherrill 2009-04-15 18:17:06 EDT
This should work now and should be fairly easily backport-able.

master:  d040ff9..8faefeb
VADER:  8ae88c8..a8c674e


The fix basically involved not setting the base channel of a reactivation token unless there is an activation token with another base channel set.

You will still get a conflicting base channel message if you have two regular activation keys with different base channels, but you should no longer receive the message if you have a single activation key with a different base channel and try to re-provision with it.
Comment 8 Steve Salevan 2009-06-05 17:55:38 EDT
VERIFIED on 5/29 build.
Comment 9 Preethi Thomas 2009-08-03 09:34:00 EDT
Release Pending
test1182.test.redhat.com
kickstarted test01-64 using rhel5u3 profile that has activation to register to clone-rhel5 channel
Comment 10 Brandon Perkins 2009-09-10 15:22:53 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html

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