Red Hat Bugzilla – Bug 1010956
rhn-proxy-activate during activation/reactivation doesn't obtain all possible options from up2date/rhn.conf
Last modified: 2015-08-10 15:47:25 EDT
Description of problem:
rhn-proxy-activate does not obtain ALL POSSIBLE options from rhn.conf like
proxy.ca_chain, proxy.http_proxy, proxy.http_proxy_username, proxy.http_proxy_password, proxy.use_ssl
Currently only 'proxy.rhn_parent' is parsed as --server
The other possible options are parsed too.
more proper string is 'default is _now_' than 'default is' to indicate that the default value is changeble.
# grep use_ssl /etc/rhn/rhn.conf
proxy.use_ssl = 1
# rhnpush --help
--no-ssl turn off SSL (not advisable), default is _now_ on.
rhn-proxy-activate should honour options from rhn.conf above ones from up2date if /etc/rhn.rhn.conf is present (i.e. during reactivation)
/etc/rhn.rhn.conf not present -> parse up2date for options
-//- present -> parse rhn.conf for options
I'm sceptical whether the parsing of up2date is needed at all.
- up2date file is parsed by configure-proxy.sh install script anyway and rhn-proxy-activate is run within using parsed options. No need for rhn-proxy-activate to parse up2date options itself.
- during reactivation only rhn.conf file matters, it shouldn't mess things with up2date.