Bug 452823

Summary: When there's no right EUS channel fail more gracefully
Product: Red Hat Enterprise Linux 4 Reporter: Michal Nowak <mnowak>
Component: up2dateAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED DUPLICATE QA Contact: Fanny Augustin <fmoquete>
Severity: low Docs Contact:
Priority: low    
Version: 4.7CC: ohudlick
Target Milestone: betaKeywords: EasyFix
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-25 12:28:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Nowak 2008-06-25 11:02:13 UTC
Description of problem:

When tried to register to EUS channel rhn.redhat.com from default 4.7 Beta
installation and the EUS channel in not on the RHN server, then up2date fails
this way:

[root@dell-pe2900-01 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux AS release 4 (Nahant Update 7 Beta)

[root@dell-pe2900-01 ~]# rhnreg_ks --username=qa --password=redhatqa
--use-eus-channel --force
While running 'registration.new_system': caught
<type 'instance'> : 'id'


It'll be much more convenient to fail with some human-readable message.

Version-Release number of selected component (if applicable):

4.7.1-17.el4

How reproducible:
always

Steps to Reproduce:
1. install 4.7 beta or other 
2. try to register with CLI tools
3. when the channel's not there (I guess), it fails oddly