Description of problem:
Setting proxy settings in rhn_register (which updates /etc/sysconfig/rhn/up2date
with proxy settings), is not copied accross to /etc/yum.conf.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run rhn_register and set proxy settings
2. Look in yum.conf and proxy settings are not set
My expectation is that yum.conf should be modified to reflect proxy settings in
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux release. Product Management has requested further review
of this request by Red Hat Engineering. This request is not yet committed for
inclusion in release.
(In reply to comment #4)
> IMO the proxy config settings should stay in /etc/sysconfig/rhn/up2date, since
> they're used by other RHN tools.
> Furthermore, I don't think it would be correct to alter the proxy behaviour for
> all yum repos. We only want to use these proxy settings with RHN. This would be
> consistant with how up2date worked.
So how yum + rhn works with proxies now (after modifiing for this bug) is at run
time we read the up2date config file, and if there is a proxy configured, then
we will use that for RHN yum repos, and only the RHN repos.
This blocker corresponds to release criteria 19c5: yum connects through
authenticated/unauthenticated http proxy from client to RHN
This should be fixed as of yum-rhn-plugin-0.1.9-3
*yum from client through RHN proxy through http proxy to RHN works
*yum from client through http proxy to RHN works
The proxy settings from /etc/sysconfig/rhn/up2date are used; no proxy settings
are in /etc/yum.conf.
Closing as the fixes are included in the latest RHEL5 trees (20061111.0)