Foreman 5.0 release candidate feedback

[ekohl]

@mhjacks

The currently packaged foremanctl package (2.3.0) wants to install foreman 3.19, which is surprising in a 5.0 release. To get 5.0, it requires going to a COPR repo, and it’s still fairly easy to get nightly images by mistake). It seems there are structural differences between the 3.19 deployments in terms of postgres version and redis→valkey and possibly role structural things. It would be really nice if foremanctl were a bit easier to customize at runtime in this way). I did a separate post about this, and it was confirmed that a 3.x version of the foremanctl RPM will ship that can deploy 5.x.

Correct: Use 5.0 containers by arvind4501 · Pull Request #753 · theforeman/foremanctl · GitHub is in Release 3.0.0 · theforeman/foremanctl · GitHub. Ideally we would have made sure that was in packaging before RC1 was announced and we did have Release foremanctl 3.0.0 by arvind4501 · Pull Request #13986 · theforeman/foreman-packaging · GitHub.

@ogajduse perhaps no pipeline was kicked off after it was merged?

@mhjacks

The currently released foreman-ansible-modules does not include the cacert parameter to the LDAP auth source module, which is usually required because of CA trust mechanics. I’m hoping there will be a 5.12 release of FAM prior to release.

Release 5.12.0