Red Hat Bugzilla – Bug 121466
Can't change base channel after upgrade to RHE-3 WS
Last modified: 2007-11-30 17:07:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922
Description of problem:
This system does not have a valid entitlement for Red Hat Network.
Please visit https://rhn.redhat.com/network/systems/entitlements.pxt
or login at https://rhn.redhat.com, and from the "Systems" tab,
select "System Entitlements" to enable RHN service for this system.
After doing an upgrade to Red Hat Enterprise 3 WS, I registered the
system. However when doing an "up2date --register", got this error
dialog. When I went to System Entitlements, the entitlement for this
system is set to "update". However its channel was the old Red Hat 9.
The problem is the base channel is set to the old Red Hat 9, and I
cannot change to Red Hat Enterprise 3 WS, (the drop down menu for Base
Channel only lists Red Hat 9 and none).
Version-Release number of selected component (if applicable):
up2date-188.8.131.52-1 / up2date-4.0.1-1
Steps to Reproduce:
1.upgrade from RH 9
2.register system with RHN
3.was unable to change system's base channel from RH9 to RH E 3 WS
Actual Results: this system (thinkpad) had update entitlement but
base channel RH9
went to systems, selected system, and change channel -- there was no
drop-down menu entry for RHE 3 WS in the base channel selection.
Expected Results: I should have been able to select RHE 3 WS in the
base channel selection, then press modify, then would have continued
with the up2date module processing.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.