Bug 812057

Summary:	Unable to directly select the RHEL 5.6 EUS base channel when currently registered with RHEL 5 base
Product:	[Retired] Red Hat Network	Reporter:	Dustin Black <dblack>
Component:	RHN/Web Site	Assignee:	rhn-dev-list
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	AMS Backlog	CC:	dblack, nbronson, nraghava, nyancey, vlaad
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-05 15:07:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dustin Black 2012-04-12 16:04:55 UTC

Description of problem:
With a system registered with the RHEL 5 base channel, if I go to the RHN web interface and click the drop-down to see the base channel options, the only other Red Hat channel available is the 5.3 Extended Update Support channel. If I select the 5.3 EUS channel and click the Modify Base Channel button, the drop-down box subsequently changes to include 5.4 EUS, 5.6 EUS, and LL options, as well as the 5.3 EUS option. I can then select the 5.6 EUS option and click the Modify Base Channel button, after which the drop-down box only has options for the RHEL 5 base channel and the 5.6 EUS channel.

How reproducible:
Consistently

Steps to Reproduce:
1. Register a RHEL 5.6 system with RHN
2. Attempt to change the base channel to 5.6 EUS, but find only 5.3 EUS available.
3. Choose the 5.3 EUS channel, then check the options again to find 5.6 EUS available, along with 5.3 EUS, 5.4 EUS, and LL.
4. Choose the 5.6 EUS channel, then check the options again to find only 5.6 EUS available.
  
Actual results:
All EUS base channels are not consistently available, based on currently-selected base channel.

Expected results:
All base channels should always be available in the drop-down.

Comment 2 Thomas "Shea" DeAntonio 2017-07-05 15:07:31 UTC

As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Comment 3 Thomas "Shea" DeAntonio 2017-07-05 15:09:50 UTC

As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).