Project

General

Profile

Actions

Bug #36927

open

After upgrade with katello-agent enabled some of the qpid-related packages remained installed

Added by Vladimir Sedmik about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

After upgrade from Katello 4.9.0 with katello-agent enabled to 4.11.0 using --whitelist=check-katello-agent-enabled some of the qpid-related packages remained installed:

qpid-proton-c-0.33.0-4.el8.x86_64
rubygem-qpid_proton-0.33.0-5.el8sat.x86_64

Actions #1

Updated by William Clark about 1 year ago

The expected behavior is that katello-agent and qpid should have been removed from the system, because the upgrade disables the feature (basically equivalent to doing `foreman-installer --foreman-proxy-content-enable-katello-agent false`) which is meant to completely remove the supporting services like qpid

My first thought is this has to do with the interaction between dnf and puppet; I suspect that these packages may not have been directly installed by puppet but were pulled in by dnf as dependencies. But when we changed the puppet package resource to have `ensure => absent` this will do something like `dnf remove $packagename` which would not necessarily remove the no-longer-needed dependencies. The puppet Package resource type has a `purgeable` feature to handle this, but the dnf provider may or may not support it, the documentation seems conflicting: https://www.puppet.com/docs/puppet/7/types/package.html#package-provider-dnf

To fully clean this up, we'll need to check whether the puppet modules can be configured to purge these dependencies with the existing package resources, or do we need to declare additional package resources to handle explicitly uninstalling them.

Actions

Also available in: Atom PDF