Bug 491876 - rhn_register fails when serverurl is not written in /etc/sysconfig/rhn/up2date
Summary: rhn_register fails when serverurl is not written in /etc/sysconfig/rhn/up2date
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhn_register
Version: 4.8
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Pradeep Kilambi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-24 14:14 UTC by Petr Sklenar
Modified: 2012-06-20 13:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:20:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of TUI debug message (136.48 KB, image/jpeg)
2009-03-24 14:14 UTC, Petr Sklenar
no flags Details

Description Petr Sklenar 2009-03-24 14:14:14 UTC
Created attachment 336476 [details]
screenshot of TUI debug message

Description of problem:
rhn_register fails when serverurl is not written in /etc/sysconfig/rhn/up2date

Version-Release number of selected component (if applicable):
rhnlib-2.1.4-4.el4
up2date-4.8.1-27.el4


How reproducible:
always

Steps to Reproduce:
1. server parent not configured in /etc/sysconfig/rhn/up2date 
2. rhn_register --serverUrl=http://xmlrpc.rhn.webqa.redhat.com/XMLRPC
  
Actual results:
TUI> some debug message in background, similar to GUI traceback, see attached screenshot

GUI> traceback

Traceback (most recent call last):
  File "/usr/sbin/rhn_check", line 259, in ?
    server = rpcServer.getServer()
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 191, in getServer
    password=proxyPassword)
  File "/usr/lib/python2.3/site-packages/rhn/rpclib.py", line 153, in __init__
    type = (string.lower(type)).strip()
  File "/usr/lib64/python2.3/string.py", line 55, in lower
    return s.lower()
AttributeError: 'NoneType' object has no attribute 'lower'
Expected results:
TUI&GUI work

Additional info:

Comment 1 Jiri Pallich 2012-06-20 13:20:31 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.