Bug 2249540

Summary: Re-registering a host with --force does not change content source
Product: Red Hat Satellite Reporter: Jeremy Lenz <jlenz>
Component: Hosts - ContentAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: Cole Higgins <chiggins>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: baitken, chiggins, gtalreja, iballou, momran, paji, rlavi, wpinheir
Target Milestone: 6.15.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:15:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Hotfix RPM for Satellite 6.13.7 on RHEL 8 none

Description Jeremy Lenz 2023-11-13 18:30:46 UTC 
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.
Comment 1 Jeremy Lenz 2023-11-13 18:30:51 UTC 
Created from redmine issue https://projects.theforeman.org/issues/36840
Comment 2 Jeremy Lenz 2023-11-13 18:30:52 UTC 
Upstream bug assigned to None
Comment 3 Bryan Kearney 2023-11-14 00:02:47 UTC 
Upstream bug assigned to jlenz
Comment 4 Bryan Kearney 2023-11-14 00:02:50 UTC 
Upstream bug assigned to jlenz
Comment 5 Bryan Kearney 2023-11-16 00:02:48 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36840 has been resolved.
Comment 10 errata-xmlrpc 2024-04-23 17:15:36 UTC 
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
Comment 11 Ian Ballou 2024-04-25 21:43:52 UTC 
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