Problem:
Rerunning failed, all, or successful jobs no longer works.
Expected outcome:
Able to rerun all, success or failed jobs.
Foreman and Proxy versions:
root@10-222-206-152:foreman-ui-01:[~]:
$ rpm -qa | grep foreman
rubygem-foreman_salt-17.0.2-1.fm3_15.el9.noarch
rubygem-foreman_vault-3.0.0-1.fm3_15.el9.noarch
rubygem-foreman_statistics-2.1.0-4.fm3_16.el9.noarch
rubygem-hammer_cli_foreman_kubevirt-0.2.0-2.fm3_16.el9.noarch
rubygem-hammer_cli_foreman_salt-0.1.0-3.fm3_16.el9.noarch
rubygem-hammer_cli_foreman_ssh-0.0.3-2.fm3_16.el9.noarch
foreman-obsolete-packages-1.11-1.el9.noarch
rubygem-hammer_cli_foreman_tasks-0.0.24-1.fm3_17.el9.noarch
rubygem-foreman_puppet-9.1.0-1.fm3_17.el9.noarch
foreman-release-3.18.1-1.el9.noarch
foreman-proxy-3.18.1-1.el9.noarch
rubygem-hammer_cli_foreman-3.18.1-1.el9.noarch
foreman-selinux-3.18.1-1.el9.noarch
foreman-3.18.1-1.el9.noarch
rubygem-foreman-tasks-11.1.1-1.fm3_18.el9.noarch
rubygem-foreman_remote_execution-16.5.3-1.fm3_18.el9.noarch
foreman-dynflow-sidekiq-3.18.1-1.el9.noarch
foreman-libvirt-3.18.1-1.el9.noarch
foreman-postgresql-3.18.1-1.el9.noarch
foreman-redis-3.18.1-1.el9.noarch
foreman-service-3.18.1-1.el9.noarch
foreman-telemetry-3.18.1-1.el9.noarch
foreman-vmware-3.18.1-1.el9.noarch
rubygem-foreman_kubevirt-0.6.0-1.fm3_18.el9.noarch
rubygem-foreman_ovirt-2.0.3-1.fm3_18.el9.noarch
rubygem-foreman_templates-11.0.1-1.fm3_18.el9.noarch
rubygem-foreman_webhooks-5.0.2-1.fm3_18.el9.noarch
foreman-cli-3.18.1-1.el9.noarch
rubygem-hammer_cli_foreman_puppet-0.1.2-1.fm3_18.el9.noarch
rubygem-hammer_cli_foreman_remote_execution-0.4.2-1.fm3_18.el9.noarch
rubygem-foreman_maintain-1.14.3-1.el9.noarch
foreman-installer-3.18.1-1.el9.noarch
Foreman and Proxy plugin versions:
All latest.
Distribution and version:
Alma Linux 9
Other relevant data:
When attempting to use the ReRun All, ReRun Successful, ReRun Failed - the hosts no longer load when you get to the host selection screen. (Its also affected by the long wait times reported here).
This error appears, but I see no corresponding error in the actual log file.
Also, when you take the search term and copy/paste it into the Host/All Hosts search bar - it fails to load.
We are considering reverting back to 3.17 - as 3.18.1 just has far too many issues with the job/task system.