Upgrading to Foreman 3.12 with ipv6 disabled

Development
1

Hello Foreman Community,

I have run an upgrade of Foreman 3.11 (Katello 4.13) to Foreman 3.12 (Katello 4.14) and I have experienced issues while running this upgrade on systems with ipv6 disabled

I did notice in the release notes that ipv4 only builds are supported. I don’t have any issues running a ground up install of Foreman 3.12 with ipv6 disabled however the upgrade from 3.11 refuses to proceed unless ipv6 is enabled.

I was able to bypass this issue by enabling ipv6 for the upgrade however I have never had issues upgrading with ipv6 disabled before 3.12 so it would seem the blockage of the upgrade is unintended

2 Likes
2

Do you have any details like an error message?

3

The foreman-installer is failing on the ipv6 check script

2024-11-20 09:07:54 [DEBUG ] [checks] Executing checker: /usr/share/foreman-installer/checks/ipv6
2024-11-20 09:07:54 [DEBUG ] [checks] Executing checker: /usr/share/foreman-installer/checks/noexec
2024-11-20 09:07:54 [DEBUG ] [pre_exit] Hook /usr/share/foreman-installer/hooks/pre_exit/20-certs_regenerate.rb returned nil
2024-11-20 09:07:54 [DEBUG ] [root] Exit with status code: 20 (signal was invalid_system)

It seems that this check was put in place to prevent the system from breaking during installs and upgrades

I am also able to upgrade when I disable this script but I am curious why this check is being done and why it is suggesting ipv6 needs to be enabled.

If enabling ipv6 does ensure the integrity of the system during upgrades I am just interested in what changed and why this is the case now

4

We added this check because in the past it’s been known to cause problems. The commit message has details: