This is with Katello 4.1.2.1 on CentOS 7.9.
For the upgrade to Katello 4 I have set up a new content proxy named foreman-content which replaces the old Katello 3 content proxy named foreman-proxy. Now I have wanted to remove the old content proxy from the system and started looking for places where it is still referenced, e.g. I have changed it in all my host groups.
I have also noticed that all my content hosts except the new ones which were registered against the new proxy from the start still reference the old content proxy, e.g. when checking with hammer:
# hammer host info --id=148
...
Content Information:
Content View:
Id: 11
Name: CentOS 7
Lifecycle Environment:
Id: 3
Name: Production
Content Source:
Id: 5
Name: foreman-proxy.example.com
...
However, there doesn’t seem to be any way to change or see this with the GUI. The Details page of a content host shows the LE and content view but not the content source. The only way to check for it seems to search for a “content_source” in the host list. There is also no way to change it except again using hammer.
None of my content hosts is actually using the old proxy anymore. I have removed the old katello-ca-consumer-foreman-proxy.dkrz.de package on all content hosts and installed the katello-ca-consumer for the new content proxy instead. All content hosts show subscribed to the new content proxy.
Yet, internally, the content source is still set to the old one. I guess, this would cause problems if I wanted to delete the old content proxy while still referenced by all those content hosts. I have changed the content source of all my content hosts now to get this information in line, even though I guess it’s not actually used and relevant unless I would maybe rebuild a host.
So I think this is quite confusing.
In the long run, it seems to me that there are two relevant hosts here: the proxy for subscription and the proxy for the actual content access. The former would be the server in /etc/rhsm/rhsm.conf, the latter is the server used in /etc/yum.repos.d/redhat.conf. That way the content source could be a normal configuration option in the gui for a content host and users could conveniently change the content source there to point all repositories to a different content proxy (instead of going through the trouble with remove and installing the katello-ca-consumer package).