Meeting Type: Foreman Release Team Meeting
Date: Jul 08, 2026
Community: https://community.theforeman.org
Foreman Nightly
- openssl is currently broken in CentOS Stream 9, causing CI failures. As a temporary workaround, downgrade openssl and openssl-libs on VMs after they are started. PRs raised in foreman-infra, forklift and foremanctl
- Pin openssl to 3.5.5-3.el9 on EL9 Jenkins nodes by Odilhao · Pull Request #2444 · theforeman/foreman-infra · GitHub
- Workaround broken openssl 3.5.7-1 on EL9 by ogajduse · Pull Request #1962 · theforeman/forklift · GitHub
- Downgrade openssl on CentOS Stream 9 VMs in CI by ehelms · Pull Request #632 · theforeman/foremanctl · GitHub
Foreman OCI Releases
- Candlepin 4.8 was released last week in Foreman nightly
- Odilon added a new stage in the katello-nightly-rpm-pipeline to build the “real” nightly.
- Containers are going to be built when the katello-nightly-rpm-pipeline passes from now on.
- Retrigger Konflux nightly component rebuilds after katello nightly pipeline by Odilhao · Pull Request #584 · theforeman/jenkins-jobs · GitHub
- Odilon is going to start working on stage → prod gating job
Foreman 3.19
- Status Updates
- Foreman 3.19.1 was released last week, containing 4 CVE fixes. See Foreman :: Security.
Foreman 3.18
- Status Updates
- CI is green
- Foreman 3.18.2 was released last week, containing 4 CVE fixes. See Foreman :: Security.
Katello 4.21
- Status Updates
- Katello 4.21.0 is released
Katello 4.20
- Status Updates
- 4.20.1 is out Katello 4.20.1 is now available
- 4.20.2 is in discussion, we’ll release if needed, but it’s less likely to happen
Pulp Integration
- Current Status
- We need to start EL10 builds.
- Pulp will be the first part to be built on top of EL10
- We’ll need to take a look at the Puppet modules to see if they can install Pulp on EL10
- We need to start EL10 builds.
Other
- How do we identify patches to be cherry-picked to stable branches?
- There is currently no standardized process for this in Foreman core. Katello runs triage meetings to review community-reported issues.
- There might be an expectation that the Foreman Release Owner identifies patches to be backported. But the Release Owner has no clue about what needs to be backported if they are not taking an active part in Foreman core development.
- Odilon likes the PR labels approach - flag issues to be backported using PR labels - and suggested using the GitHub milestones feature
- Ian will post a community RFC to discuss this further