Bug #38066
open
Starting with 3.12, TheForeman refuses to install without IPv6
Description
Apparently, this is related to Feature #37693 . The feature was not implemented correctly.
Several problems:
- It is an undocumented change (I didn't see it in the release notes or in the prerequisites)
- It breaks Foreman in organizations that, by policy, disable IPv6.
- Because it is undocumented, the issue occurs halfway through the upgrade process from 4.11 to 4.12. Enabling IPv6 requires a reboot with the new RPMs but without foreman-installer having successfully completed.
The proper solution to the issue would have been to remove the dependencies on IPv6.
Updated by Kevin Keane about 2 months ago
- Related to Feature #37693: Add check for ipv6.disable=1 in /proc/cmdline because it's known to break installations added
Updated by Mate Mikulic 11 days ago
ยท Edited
Kevin Keane wrote:
Apparently, this is related to Feature #37693 . The feature was not implemented correctly.
Several problems:
- It is an undocumented change (I didn't see it in the release notes or in the prerequisites)
- It breaks Foreman in organizations that, by policy, disable IPv6.
- Because it is undocumented, the issue occurs halfway through the upgrade process from 4.11 to 4.12. Enabling IPv6 requires a reboot with the new RPMs but without foreman-installer having successfully completed.The proper solution to the issue would have been to remove the dependencies on IPv6.
I totally agree with this.
IPv6 is not widely accepted, especially in companies internal infrastructure with VPN and private IPv4 ranges.
There is no need to switch to IPv6 in such scenarios, and security standards are there to be upheld.
It would be better to have an clause in installer script, if IPv6 enabled, listen ::1, if not, remove the line.