Bug 491816 - after re-registration to new RHN server, only 'serverURL=' is updated, 'noSSLServerURL=' stays old
after re-registration to new RHN server, only 'serverURL=' is updated, 'noSSL...
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
4.8
All Linux
low Severity low
: rc
: ---
Assigned To: Pradeep Kilambi
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-24 04:47 EDT by Jan Hutař
Modified: 2012-06-20 11:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 11:57:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2009-03-24 04:47:52 EDT
Description of problem:
After the re-registration to new RHN server, only 'serverURL=' in /etc/sysconfig/rhn/up2date is updated, 'noSSLServerURL=' stays old.


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


How reproducible:
always


Steps to Reproduce:
1. # grep -i serverURL= /etc/sysconfig/rhn/up2date
   noSSLServerURL=http://xmlrpc.rhn.redhat.com/XMLRPC
   serverURL=https://xmlrpc.rhn.redhat.com/XMLRPC
2. # up2date --register   # in GUI, change RHN server URL in "Network
   settings" dialog (in my case it was "...rhn.redhat.com..." -> 
   "...rhn.stage.redhat.com...")
3. # grep -i serverURL= /etc/sysconfig/rhn/up2date
   noSSLServerURL=http://xmlrpc.rhn.redhat.com/XMLRPC
   serverURL=https://xmlrpc.rhn.stage.redhat.com/XMLRPC


Actual results:
noSSLServerURL=http://xmlrpc.rhn.redhat.com/XMLRPC
serverURL=https://xmlrpc.rhn.stage.redhat.com/XMLRPC


Expected results:
noSSLServerURL=http://xmlrpc.rhn.stage.redhat.com/XMLRPC
serverURL=https://xmlrpc.rhn.stage.redhat.com/XMLRPC


Additional info:
Maybe this is expected behaviour, but it seems odd to me - is this a NOTABUG?
Comment 1 Jiri Pallich 2012-06-20 11:57:58 EDT
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.