Description of problem: When static IPv6 address is specified during deployment and IPv4 is disabled, ovirt-hosted-engine-setup leaves IPV6_AUTOCONF (SLAAC) enabled by default ("ipv6.method = auto"). If there is a network issue and router advertisement ICMPv6 responses are not received, NetworkManager fails to configure interface and HE becomes unreachable. According to RHEL 8 configuration guide [1], for static address configuration, "ipv6.method = manual" must be specified. [1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-an-ethernet-connection_configuring-and-managing-networking Version-Release number of selected component (if applicable): ovirt-host-4.5.0-3.el8ev.x86_64 ovirt-hosted-engine-setup-2.6.4-1.el8ev.noarch How reproducible: Always Steps to Reproduce: 1. Deploy HE with IPv6 static address only (no IPv4). 2. Verify NM connection configuration. Actual result: # nmcli con show "System eth0" | grep ipv6.method ipv6.method: auto Expected result: # nmcli con show "System eth0" | grep ipv6.method ipv6.method: manual Additional information: - Issue found on associated case.
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.
Works for me on latest components. Moving to verified. Please reopen if you still see any issues.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHV Engine and Host Common Packages update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8503