When migrating systems using bootstrap.py, an existing katello-ca-consumer bundle can be removed by: call_yum("remove", "'katello-ca-consumer-*' katello-agent gofer katello-host-tools katello-host-tools-fact-plugin", False) On some versions of the RPM, removal will cause the /etc/rhsm/rhsm.conf to be replaced with /etc/rhsm/rhsm.conf.kat-backup which was created when the RPM was originally installed. The issue arises when the customer has made a change to their proxy configuration in /etc/rhsm/rhsm.conf after the kat-backup file was created, so reverting to the kat-backup breaks the proxy configuration for RHSM. A note in the Satellite documentation to be aware of this behavior when migrating systems with bootstrap.py could help to save a lot of troubleshooting time for the customer.
Hi William, Thank you for opening this ticket.
While this is a corner case, I would prefer that we solve this via a capability in the bootstrap script itself to 'preserve proxy' when reconfiguring/migrating the client. Moving to the bootstrap component.
https://github.com/Katello/katello-client-bootstrap/pull/283 was merged → POST
in the upstream, bootstrap.py now implements the option `--preserve-rhsm-proxy` which retrieves the current http proxy server configuration from /etc/rhsm/rhsm.conf and re-applies it to the same file after the file has been modified by installing the katello-ca-consumer*.rpm
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222