Bug 714085

Summary:	when I register normal (non EUS) RHEL5 system to rhn.redhat.com, I get EUS channel instead of regular one
Product:	[Retired] Red Hat Network	Reporter:	Jan Hutař <jhutar>
Component:	RHN/Registration	Assignee:	Sebastian Skracic <sskracic>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Network Quality Assurance <rhn-qa-list>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	rhn522	CC:	ahamilton, atodorov, cperry, dgregor, ggainey, gholms, jneedle, jpazdziora, mihai.ibanescu, nbronson, pskopek, rbiba, rrajasek, xdmoon
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-15 20:45:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	545868

Description Jan Hutař 2011-06-17 10:39:47 UTC

Description of problem:
when I register normal (non EUS) RHEL5 or RHEL6 system to rhn.redhat.com, I get EUS channel instead of a regular one.


Version-Release number of selected component (if applicable):
rhn-check-1.0.0-61.el6.noarch
rhn-client-tools-1.0.0-61.el6.noarch
rhnlib-2.5.22-10.el6.noarch
rhnsd-4.9.3-2.el6.x86_64
rhn-setup-1.0.0-61.el6.noarch
yum-rhn-plugin-0.9.1-26.el6.noarch


How reproducible:
always


Steps to Reproduce:
1. Install RHEL6 system and register to Prod
   # rhnreg_ks --username...
2. # yum repolist
   [...]
   rhel-x86_64-server-6.1.z
3. # rm -rf /etc/yum.repos.d/*
4. In WebUI switch to common RHEL6 channel
5. # yum repolist
   [...]
   rhel-x86_64-server-6
6. # yum list extras
   <only my custom packages which should not impact tis>


Actual results:
After registration (I do not have org. default activation key which could have cause this) I got rhel-x86_64-server-6.1.z


Expected results:
I should have rhel-x86_64-server-6


Additional info:
When I have tried to register against Satellite, I got correct rhel-x86_64-server-6 channel directly.

Comment 6 Sebastian Skracic 2011-06-20 09:26:20 UTC

*** Bug 714304 has been marked as a duplicate of this bug. ***

Comment 7 Mihai Ibanescu 2011-06-20 14:15:21 UTC

Any ETA?

Comment 8 Peter Skopek 2011-06-20 14:25:30 UTC

This bug is a blocker for our automated rpm testing of JBoss products.
I am rising priority.

Comment 9 Clifford Perry 2011-06-20 14:56:23 UTC

In my own testing, when I encountered this bug:

The work around for this issue is to login to the RHN Classic (rhn.redhat.com) interface and manually re-subscribe it to the correct base channel and not the EUS channel. 

Cliff

Comment 11 Mihai Ibanescu 2011-06-20 15:09:39 UTC

Cliff, you are right, for manually getting around this problem, that works. The problem is with automated tests that rely on the correct behavior of channel assignment, as Peter pointed out in comment 8.

Comment 19 Andrew Hamilton 2011-06-22 21:08:07 UTC

A possible temporary workaround for this is to use the RHN API. You can use the setBaseChannel() call with a script (Python, PERL, etc) to automate the change the base channel after registration with RHN.

An quick example setup can be found here: http://pastebin.com/y45rmy2X . This contains a BASH script to get the system ID of the RHEL installation and then a python script to change the base channel. If you wish to change the base channel to something other than the RHEL v. 5 channel then you must change the Channel ID that is sent. Information on finding the channel ID can be found here: https://access.redhat.com/knowledge/docs/Red_Hat_Network/Reference_Guide/s1-rhn-api-cid.html

Andrew

Comment 20 Grant Gainey 2011-06-22 21:16:43 UTC

Nice - that's a great idea, Andrew.

Comment 21 Grant Gainey 2011-06-26 01:43:10 UTC

Fix is now in production - we should be good to go

Comment 22 Radek Bíba 2011-07-01 08:58:11 UTC

Please fix Stage too.

Comment 23 Radek Bíba 2011-07-01 08:58:45 UTC

...I mean errata.stage.

Comment 26 Rajesh Rajasekaran 2011-07-15 12:28:56 UTC

Please apply this fix to errata.stage. All our automated testing from stage are blocked due to this issue.

Comment 28 Stephen Herr 2011-07-15 20:44:23 UTC

The fix has been applied to errata.stage. Please try your tests again, this should be fixed now.