@evgeni : the issue is for a fresh install of katello 3.18, or update foreman 2.3/katello 3.18 before upgrading to foreman 2.4/katello 4.0.
Can the rpm dependencies beeing corrected for katello 4.0
be backported for katello 3.18 rpms (server & clients) ?
Exactly right. Best case scenario - user hits an upgrade bug from 3.18 → 4.0; we work around it somehow. That might mean pushing a fix into the KATELLO-3.18 branch to be applied manually by the user, but nothing beyond that.
Anyone looking to install a fresh Katello system should absolutely install Katello 4.2 which is now GA!
I installed Katello 4.2-RC2 on a test system, no issues at all. Very excited to see 4.2.0 in GA! Time to wipe my production (3.18) system clean and start new.
I’m actually running into this issue right now. I have Katello 3.18.4 deployed on RHEL7. I’m trying to upgrade to Katello 3.18.5 before upgrading to Katello 4.0.
Should I just skip 3.18.5 and go directly to Katello 4.0?
Thanks for the repository, at least yum doesn’t throw errors about qpid anymore.
Now I can finally update from Foreman 2.5.1/Katello 4.1.0 to the latest patch,
which should fix some of the issues we have.