foreman-nightly-rpm-pipeline 1501 failed

Foreman RPM nightly pipeline failed:

foreman-pipeline-foreman-nightly-almalinux8-install (passed) (remote job)
foreman-pipeline-foreman-nightly-almalinux8-upgrade (failed) (remote job)
foreman-pipeline-foreman-nightly-centos7-install (passed) (remote job)
foreman-pipeline-foreman-nightly-centos8-stream-upgrade (failed) (remote job)
foreman-pipeline-foreman-nightly-centos8-stream-install (passed) (remote job)
foreman-pipeline-foreman-nightly-centos7-upgrade (passed) (remote job)

2022-06-09 22:31:04 [INFO  ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: Foreman::PluginRequirementError: ERF72-7165 [Foreman::PluginRequirementError]: foreman_puppet 
plugin requires Foreman >= 3.3.0 but current is 3.2.1

But how did that system end up with rubygem-foreman_puppet-4.0.1-1.fm3_3.el8 installed?!

Interestingly, it also has foreman-release-3.3.0-1.el8.noarch installed :confused:

Ooooh. We don’t enable the right module on upgrade, I think, and we dropped module_hotfixes=1 the other day from the 3.3 repos.

Should be fixed by use foreman_repositories from the operations collection by evgeni · Pull Request #1513 · theforeman/forklift · GitHub

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.