Description of problem ====================== Given I have an IPv6 only host When I deploy Hosted-Engine using the '--6' flag (to force deploy over IPv6) Then the deploy fails while the newly installed RHV VM tries to add the host to the cluster Version-Release number of selected component (if applicable) ============================================================ Host -> rhvh-4.4.9.2-0.20211011.0+1 Appliance -> rhvm-appliance-4.4-20210827.0.el8ev.x86_64.rpm How reproducible ================ 100% Steps to Reproduce ================== 1. Provision a host with RHV-H OS: rhvh-4.4.9.2-0.20211011.0+1 2. dnf install 'rhv-release-4.4.9' on the host (rhv-release-4.4.9-7-001.noarch) 3. dnf install 'rhvm-appliance' on the host (rhvm-appliance-2:4.4-20210827.0.el8ev.x86_64) 4. Make host IPv6 only using nmcli (nmcli connection modify <interface> ipv4.method disabled ipv6.method manual ipv6.addresses <IPv6 static address> ipv6.dns <IPv6 DNS address> ipv6.gateway <IPv6 gateway address>) 5. Reload <interface> (nmcli con down <interface> ; nmcli con up <interface>) 6. Execute 'command hosted-engine --deploy --6' Actual results ============== Deploy fails during the stage where the host is added to the cluster [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} Expected results ================ Deploy is successful Additional info =============== * This also reproduces on a dual-stack IP host (both IPv4 and IPv6) * An answer file is used in the deploy * Possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=2010640
Tentatively targeting to 4.4.10, but it purely depends on platform bug BZ2010640
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
doesn't affect runtime, just deployment. workaround possible with manual hook-based route fix up. demoting to High.
Verified on - rhvm-4.4.9.5-0.1.el8ev.noarch with rhvm-appliance-4.4-20211111.1.el8ev.x86_64 rhvh-4.4.9.2-0.20211104.0+1
This bugzilla is included in async oVirt engine release for oVirt 4.4.9 release, published on November 11th, 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.9 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.
This bug report has been also tested and verified without using the HE offline mode using: rhvm-appliance-4.4-20211117.1.el8ev.x86_64 - which contains the fix for BZ 2024142 rhvh-4.4.9.2-0.20211117.0+1
Ales/Martin, should engine 4.4 be able to deploy RHEL 7 hosts (on cluster-level 4.3)? If so then this patch broke it, I removed the "nmcli general reload conf" part of it to be able to deploy
(In reply to Arik from comment #17) > Ales/Martin, should engine 4.4 be able to deploy RHEL 7 hosts (on > cluster-level 4.3)? > If so then this patch broke it, I removed the "nmcli general reload conf" > part of it to be able to deploy Thanks created BZ2032919 to track this issue
Thanks