Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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