Red Hat Bugzilla – Bug 146498
up2date isn't Satellite Server Aware
Last modified: 2007-11-30 17:07:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
When prompting for Channels to update, the GUI up2date has a link to
hosted RHN hardcoded into the button for the "To Subscribe or
unsubscribe from channels..." text. This button actually takes one to
rhn.redhat.com in a mozilla window as well.
This button should instead pick up the config value serverURL and use
it if it is not rhn.redhat.com.
This is going to be a FAQ for many users.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.run up2date as root from a xterm
3.read button in middlw of window
Actual Results: You get a button that sends you to rhn.redhat.com
Expected Results: You get a button that sends you to the vaule of
Internal RFE bug #147223 entered; will be considered for future releases.
Hurm.. revisiting becase this is listed in our internal issue tracking system
and I was playing cleanup today and found this one which I had forgotten.
The reason for asking for serverURL to be used if differnt from rhn.redhat.com
is because the current functionality makes up2date confusing for people with a
RHN Satellite. Specificlly, users are redirected to RHN Hosted which has no
concept of who the site Satellite users are.
Since 147223 is private, could someone please update that bug with this information?
Also, since appears to be a regression in user experince for RHN Satellite
users, I think perhaps this is truly a UI bug instead of an RFE.
Internal RFE updated with additional information.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.