Problem:
Foreman 3.17.0 seems to require Puppet 8 or above:
[root@foreman ~]# foreman-installer --noop --verbose
2025-12-25 22:53:13 [NOTICE] [root] Loading installer configuration. This will take some time.
Puppet 7.34.0 does not meet requirements for puppetlabs-apache (>= 8.0.0 < 9.0.0)
Cannot continue due to incompatible version of Puppet. Use --skip-puppet-version-check to disable this check.
2025-12-25 22:53:19 [ERROR ] [root] Puppet 7.34.0 does not meet requirements for puppetlabs-apache (>= 8.0.0 < 9.0.0)
2025-12-25 22:53:19 [ERROR ] [root] Incompatible version of Puppet used, cannot continue
The upgrade instructions don’t mention upgrading Puppet, but probably should.
In section 3.1.3, there’s a chart of supported Puppet versions, but 7.x is still listed as supported.
In post-upgrade steps 3(A) the instructions say the output of foreman-rake db:migrate and db:seed should output nothing. On my systems they output:
[root@foreman ~]# foreman-rake db:migrate
== 20250109165511 RemoveTaxonomyAndOverrideFromFilter: migrating ==============
-- remove_column(:filters, :override)
-> 0.0790s
== 20250109165511 RemoveTaxonomyAndOverrideFromFilter: migrated (0.2530s) =====
== 20251015113343 ClearHostOwnerSetting: migrating ============================
== 20251015113343 ClearHostOwnerSetting: migrated (0.0013s) ===================
[root@foreman ~]# foreman-rake db:seed
User with login admin already exists, not seeding as admin.
The DB migrations look reasonable based on the dates, and I guess db:seed is okay? Running them a second time did result in no output.