Release Team Meeting 2026-03-11

Release Team Meeting 2026-03-04

Meeting Type: Foreman Release Team Meeting
Date: March 11, 2026
Community: https://community.theforeman.org


Foreman Nightly

Foreman 3.18

  • Status Updates
    • 3.18.0 released today - March 11: Foreman 3.18.0 is now available
    • CI is green except for one UI test failure
    • 3.18.1 is planned to be released on March 17

Foreman 3.17

Foreman 3.16


Katello 4.20

Katello 4.19


Pulp Integration

  • Current Status
    • Evgeni requested cherry-picks to 3.85
    • Katello 4.21 to be updated to pulpcore 3.105
      • We’ll need a new Postgres with 3.105 because of Django
    • We don’t know when Pulp 4 is going to be released, yet (Django 5)
    • We can’t update to past Postgres 13 at the moment, most likely due to Candlepin??

I stumbled over Puppet 7 being no longer supported by the installer at least by Foreman 17.1, which is not mentioned anywhere.

# foreman-installer
2026-03-11 17:02:27 [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.
2026-03-11 17:02:31 [ERROR ] [root] Puppet 7.34.0 does not meet requirements for puppetlabs-apache (>= 8.0.0 < 9.0.0)
2026-03-11 17:02:31 [ERROR ] [root] Incompatible version of Puppet used, cannot continue

Interesting. What environment did you reproduce it in?
I wonder if that’s something that our CI should have caught.

We dropped Puppet 7 support in Drop Puppet 7 support · theforeman/foreman-installer@59ef3ea · GitHub but it seems we never wrote a release note about this :frowning:

1 Like

It was my normal CentOS Stream 9 demo system where I already wanted to switch to OpenVox but did not find the time for. Now I had a good reason to do it during the update.

I am also not sure if the package update should already have revealed this instead of the installer complaining after everything already being updated.

Yeah, updating package dependencies is probably a good idea too.

1 Like

can be backported to 3.18 and 3.17 then

1 Like

Backport:

3.18

3.17

3 Likes

Merged it! Thanks @evgeni and @ogajduse!

2 Likes