Problems with my content views not pushing out the correct data

Support
1

We use 3 different waves in our environment Prod, PreProd, and Dev. We have 3 patchgroups which some of each wave are pulled in the a patchgroup and its the patchgroup listing of hosts that we patch monthly…

So this month we patched a host qa16 (running Rocky Linux 8) which is in a wave that this month got a new publication of patches. The host for some reason did not get the newest kernel patch this month and for some reason is still running 4.18.0-553.22.1.el8_10.x86_64. There is nothing preventing it from getting the latest kernel as far a yum.conf or dnf.conf goes. We do not use rpm lock or what ever its called.

When I go on to the host qa16 and do a yum clean all then do a yum upgrade I am showing no patches. When I look at the host in Foreman GUI and search for kernel I see the current kernel version listed above.

We do know they are up to 4.18.0-553.47 now and we do have one machine in our environment that has kernel 4.18.0-553.4x on it. So that means that 4.18.0-553.4x is some where in the local repo in foreman.

  1. Is there a way to see the exact rpms available in a Composite Content View? Meaning, I would like to see the rpms this CCV has that it can present to hosts. Not what it presented to this host.
  2. Any clue how I can try to track down why this host at least is not getting the updated RPMs we think it should be getting?
2

Yes. In the content view details page (Content > Content Views > click your CCV), go to the Versions tab and click on the current version. You will see every RPM in the content view version. You can even compare two different versions if you wish.

Are content view filters in use? Other than that, check the basics:
https://docs.theforeman.org/nightly/Managing_Content/index-katello.html#Restricting_Hosts_Access_to_Content_content-management

3

I had no idea that you could even click on those things.

In the end we found at least one of the CCVs some how was missing rpms. So we republished the patches. I kinda remember issues like this back when Katello 4 first came out too.

1 Like