Problem:foreman-maintain packages update fails due to conflicting Ruby gem dependencies between Katello and Foreman plugins.
Expected outcome: Package updates should complete successfully without dependency conflicts.
Foreman and Proxy versions: Foreman 5.0 / Katello 5.0. Proxy version not provided.
Foreman and Proxy plugin versions: hammer_cli_katello 5.0.2; hammer_cli_foreman_tasks 0.0.25 installed, 0.1.0 available; hammer_cli_foreman_remote_execution 0.4.6 available.
Distribution and version: Rocky Linux 9 (EL9)
Other relevant data:Issue first encountered October 15, 2026. dnf clean all and fresh repository metadata did not resolve the conflict. Full DNF error output and troubleshooting details included below.
-
Foreman 5.0 / Katello 5.0
-
Rocky Linux 9
-
Repositories: foreman, foreman-plugins, katello
Issue:
Routine package updates were working normally until October 15, 2026. Running foreman-maintain packages update now fails due to conflicting Ruby gem dependencies.
DNF error:
Problem 1:
package rubygem-hammer_cli_katello-5.0.2-1.el9.noarch
requires (rubygem(hammer_cli_foreman_tasks) >= 0.0.20
with rubygem(hammer_cli_foreman_tasks) < 0.1)
cannot install both:
rubygem-hammer_cli_foreman_tasks-0.1.0-1.fm5_0.el9
rubygem-hammer_cli_foreman_tasks-0.0.25-2.fm5_0.el9
Problem 2:
rubygem-hammer_cli_foreman_remote_execution-0.4.6-1.fm5_0.el9
requires (rubygem(hammer_cli_foreman_tasks) >= 0.1.0
with rubygem(hammer_cli_foreman_tasks) < 1)
The Foreman Plugins 5.0 repository offers rubygem-hammer_cli_foreman_tasks-0.1.0, which is incompatible with the dependency requirements of rubygem-hammer_cli_katello-5.0.2.
The package update exits with status 1.
Troubleshooting performed:
Ran dnf clean all and refreshed repository metadata. The same conflicting packages are still being offered.
No packages were forcibly upgraded or removed.
Question for maintainers:
Is this a known packaging regression in Foreman/Katello 5.0?
It appears hammer_cli_katello 5.0.3 may contain updated dependency requirements that resolve this conflict. Is the corrected RPM scheduled for publication in the Katello 5.0 EL9 repository?
This is a production installation, so I would prefer to wait for corrected repository packages rather than use --allowerasing or --skip-broken.