Now that Foreman 3.7 has a release candidate, this is the place to provide your feedback. Whether it’s (possible) bugs thoughts the interface or workflow. If you’re sure it’s a bug, a new Redmine issue can also be used.
I tried upgrading my 3.6 instance and go the following error on dnf upgrade step
Foreman 3.7 509 kB/s | 1.4 MB 00:02
Foreman plugins 3.7 1.1 MB/s | 1.8 MB 00:01
Last metadata expiration check: 0:00:02 ago on Mon 29 May 2023 12:01:25 PM CEST.
Error:
Problem 1: cannot install the best update candidate for package foreman-installer-1:3.6.1-1.el8.noarch
- nothing provides puppet-agent >= 7.0.0 needed by foreman-installer-1:3.7.0-0.4.rc2.el8.noarch
Problem 2: package foreman-installer-1:3.6.1-1.el8.noarch requires rubygem(kafo) < 7.0.0, but none of the providers can be installed
- cannot install both rubygem-kafo-7.0.0-1.el8.noarch and rubygem-kafo-6.5.0-1.el8.noarch
- problem with installed package foreman-installer-1:3.6.1-1.el8.noarch
- cannot install the best update candidate for package rubygem-kafo-6.5.0-1.el8.noarch
- nothing provides puppet-agent >= 7.0.0 needed by foreman-installer-1:3.7.0-0.4.rc2.el8.noarch
The step of upgrading Puppet repo should also be listed in both
https://docs.theforeman.org/3.7/Upgrading_and_Updating/index-katello.html#Upgrading_Server_upgrade-guide
https://theforeman.org/manuals/3.7/index.html#3.6Upgradeto3.7
In my case I had to remove dnf remove puppet6-release and dnf install https://yum.puppetlabs.com/puppet/puppet-release-el-8.noarch.rpm, then the dnf upgrade worked.
I think puppet-release is Puppet 8 and we’re not testing compatibility of that. I’d recommend puppet7-release for now. For me it worked to simply run:
dnf install https://yum.puppet.com/puppet7-release-el-8.noarch.rpm
That replaced puppet6-release and upgraded the release file. I haven’t tested it with a puppetserver install present though.