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.

If you create a host that uses an external smart proxy as a content source, for example, and then register the host again using no content source (aka pulp primary), the content source won't actually be changed. This can cause errors during registration, like:

Validation failed: Host centos9-stream.example.com: Cannot add content view environment to content facet. The host's content source 'centos8-proxy-devel.example.com' does not sync lifecycle environment 'Library'. (HTTP error code 422: Unprocessable Entity)

My smart proxy didn't sync library, but the new activation key I was using was set to use library. This should work, so we need to make sure the content source is changed during re-registration.

Created from redmine issue https://projects.theforeman.org/issues/36840

Upstream bug assigned to None

Upstream bug assigned to jlenz

Upstream bug assigned to jlenz

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36840 has been resolved.

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 (Important: Satellite 6.15.0 release), 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-2024:2010

Created attachment 2029219 [details]
Hotfix RPM for Satellite 6.13.7 on RHEL 8

A hotfix RPM is available for this BZ for Satellite 6.13.7

INSTALL INSTRUCTIONS:

1. Create a complete backup or snapshot of Satellite 6.13.7 server

2. Download the hotfix RPM from this attachment

3. # dnf install ./rubygem-katello-4.7.0.36-2.HOTFIXRHBZ2249540.el8sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart