Red Hat Bugzilla – Bug 1010956
rhn-proxy-activate during activation/reactivation doesn't obtain all possible options from up2date/rhn.conf
Last modified: 2018-04-09 06:40:41 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.
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.
This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED.
Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.