Red Hat Bugzilla – Bug 450954
Currently reprovisioning with a new base channel (via activation key) doesnt' work
Last modified: 2010-10-22 21:51:45 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.
*** Bug 449846 has been marked as a duplicate of this bug. ***
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.
This should work now and should be fairly easily backport-able.
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.
VERIFIED on 5/29 build.
kickstarted test01-64 using rhel5u3 profile that has activation to register to clone-rhel5 channel
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.