Ubuntu systems showing lots of core packages as non-compliant. #8502
ppanon2022
started this conversation in
General
Replies: 1 comment
-
I ran a reindex database with Uyuni shut down, Then when I bought it back up, I ran a package list refresh, however that seemed to make no difference in the long list of packages showing up as non-compliant. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've noticed that a lot of our Ubuntu client systems are now showing a lot of core packages as non-compliant.
On one client system, running apt list --upgradeable (and afterwards apt update && apt upgrade) showed many outstanding updates from the "Non-compliant" list. Forcing a package list update from the Uyuni console doesn't change the result. Applying the updates with apt upgrade on the client made those packages disappear from the non-compliant list. Is anybody else experiencing the same problem?
In our case, I'm not exactly sure what caused it. We skipped upgrading to 2024.01 and went straight from 2023.12 to 2024.02. We also had an issue with some package syncs failing due to needing to increase available storage. So I can't know which of those changes/issues caused the change in behaviour. However I'm not seeing the same problems with rpm based distros like CentOS, OpenSUSE, or Redhat on two different servers. So I'm leaning to thinking it's likely due to a change in the package comparison/matching algorithm for the on-compliant list. Was there any change affecting that in 2024.01 or 2024.02?
This is very concerning because it means needed Ubuntu updates are not being deployed.
Beta Was this translation helpful? Give feedback.
All reactions