Problem: Upgrading Foreman to 3.11.x results in the WebUI seemingly not being able to retrieve most forms of data.
Expected outcome: Upgrading from 3.10 should result in a fully functional system.
Foreman and Proxy versions: 3.9.3/4.11.1 → 3.10.1/4.12.1 → 3.11.4/4.13.1
Distribution and version: RHEL 8.10
Other relevant data: Logs to be re-aggregated.
The system in question has been reset to 3.9.3 via snapshot, but I am currently trying to bring our systems back into a supported release cycle (was planning to go to 3.12/4.14). I made numerous attempts to do so on a fully up-do-date system, however every time I make the bump from 3.10 to 3.11 the system ends up in a bugged state. Using hammer on the host seems mostly okay, though very delayed in responses. The WebUI on the other hand is full of endless loading icons, from the default dashboard page to content, tasks, and content pages.
foreman-maintain health check and foreman-maintain service status all return green after upgrading. I’ve followed the documentation on the upgrade verbatim (though I do have to manually patch katello-certs-check after the package updates and before running foreman-installer (L160?) to remove the OpenSSL 3.x-only flags.
I’ve marked logs here as TBD as I will need to rerun the entire chain of upgrades once again.
Has anyone else run into this issue by chance?