Red Hat Bugzilla – Bug 502915
Teach rhn-register to know about multiple z stream channels per redhat-release
Last modified: 2015-01-04 16:56:54 EST
Re-verified in staged (Satellite-5.3.0-RHEL5-re20090724.0) with pushed package updates from Aug 12 On a client rlx-3-24 with Red Hat Enterprise Linux Server release 5.3 (Tikanga) [root@rlx-3-24 ~]# rhnreg_ks --serverUrl=http://test1182.test.redhat.com/XMLRPC --username=john --password=dog8code --force --profilename=rlx-3-24EUS --use-eus-channel The base channel selected by satellite was: RHEL Extended Update Support (v. 5.3.z for 32-bit x86) Registering the client without --use-eus-channel [root@rlx-3-24 ~]# rhnreg_ks --serverUrl=http://test1182.test.redhat.com/XMLRPC --username=john --password=dog8code --force --profilename=rlx-3-24 The base channel selected by satellite was: Red Hat Enterprise Linux (v. 5 for 32-bit x86) And finally if I remove the entitlements to the EUS channel, and try to register with --use-eus-channel the base rhel channel gets subscribed to. [root@rlx-3-24 ~]# rhnreg_ks --serverUrl=http://test1182.test.redhat.com/XMLRPC --username=john --password=dog8code --force --profilename=rlx-3-24EUS --use-eus-channel The base channel selected by satellite was: Red Hat Enterprise Linux (v. 5 for 32-bit x86) in Comment #3, Garik suggests that he has to choose channel "(none, disable service)" first when trying to change the registered system from an EUS base channel to the the base Rhel channel. I did not have to do that. I could modify the base channel directly. Attaching a screenshot. I believe this behaviour is best and correct. The same verification was done for a client with Red Hat Enterprise Linux AS release 4 (Nahant Update 8) when registering with --use-eus-channel resulted in subscription to RHEL AS Extended Update Support (v. 4.8.z for 32-bit x86) Moving to RELEASE_PENDING
Created attachment 357470 [details] client registered with --use-eus-channel can alter base channel back to the base Rhel 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. http://rhn.redhat.com/errata/RHEA-2009-1434.html