Currently, when a new machine is registered (or, when
ignore_facts_for_operatingsystem=false, after a while™ ) new OSes start to turn up in the Operating Systems list.
Rocky 8.5 etc.
However, in my situation this breaks some deployment related settings, as I have Ansible only define them for the OS major version (so,
I have successfully worked around this by setting
true for all machines that are deployed by Foreman, so they’ll stick to
Rocky 8 as their OS with all the settings I’ve made.
Except when I manually register a system that’s been freshly installed from the ISO. Because the
/etc/os-release is set as
8.5 Foreman then continues to create that OS in the registration proces. Which then allows other machines to also become set to that OS version and break everything again
Is there, except editing
/etc/os-release to remove the
.5 from the
VERSION_ID a way of telling Foreman to not do that? (IMHO, I never used any of the auto-detected OSes, so I could do without, but I’m not sure if other folks around use it).
To clarify, I’d like Foreman to stop considering all the minor versions as actual OSes (CentOS7 was a nightmare with the gazillion minor versions that were detected). Just stick to majors
Not automatically break OS re-deployment for existing machines