Description of problem: If HE deployment fails and the customer needs to repeat it, the setup fails when adding ipv6 rules that already exist. This is because cleanup just remove ipv4 ones: ovirt-hosted-engine-setup/src/bin/ovirt-hosted-engine-cleanup 37 remove_ip_rules(){ 38 for rule in $(ip rule | grep 10* | cut -d':' -f1) 39 do 40 ip rule del prio $rule 41 done 42 } See: # ip -6 rule show 0: from all lookup local 101: from fd00:1234:5678:900::1/64 lookup main 32766: from all lookup main # for rule in $(ip rule | grep 10* | cut -d':' -f1); do ip rule del prio $rule; done Still here: # ip -6 rule show 0: from all lookup local 101: from fd00:1234:5678:900::1/64 lookup main 32766: from all lookup main The 'ip rule' command won't show that ipv6 rule: # for rule in $(ip rule | grep 10* | cut -d':' -f1); do echo $rule; done We need ip -6 rule: # for rule in $(ip -6 rule | grep 10* | cut -d':' -f1); do echo $rule; done 101 Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.3.13-2.el7ev.noarch (customer)
Works fine on these components on host: rhvm-appliance-4.4-20210402.1.el8ev.x86_64 ovirt-hosted-engine-ha-2.4.6-1.el8ev.noarch ovirt-hosted-engine-setup-2.5.0-2.el8ev.noarch openvswitch2.11-2.11.3-87.el8fdp.x86_64 Linux 4.18.0-305.el8.x86_64 #1 SMP Thu Apr 29 08:54:30 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.4 (Ootpa) Components on engine: ovirt-engine-setup-4.4.6.7-0.1.el8ev.noarch openvswitch2.11-2.11.3-87.el8fdp.x86_64 Linux 4.18.0-305.el8.x86_64 #1 SMP Thu Apr 29 08:54:30 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.4 (Ootpa)
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 RHEL Host (ovirt-host) [ovirt-4.4.6]), 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-2021:2178
Due to QE capacity, we are not going to cover this issue in our automation