Hi team, One of my customers is also hitting this bug but they could update their cluster in a short time frame. Do we have any workaround for this issue ? Thanks a lot! Best Regards, Chen
*** Bug 2022703 has been marked as a duplicate of this bug. ***
Verified this bug on 4.6.0-0.nightly-2021-12-01-180138
sh-4.4# iptables-save | grep -i ICMP :AZURE_CHECK_ICMP_SOURCE - [0:0] :AZURE_ICMP_ACTION - [0:0] -A INPUT -p icmp -m icmp --icmp-type 3/4 -j AZURE_CHECK_ICMP_SOURCE -A OPENSHIFT-BLOCK-OUTPUT -p tcp -m tcp --dport 22623 --tcp-flags FIN,SYN,RST,ACK SYN -j REJECT --reject-with icmp-port-unreachable -A OPENSHIFT-BLOCK-OUTPUT -p tcp -m tcp --dport 22624 --tcp-flags FIN,SYN,RST,ACK SYN -j REJECT --reject-with icmp-port-unreachable -A AZURE_CHECK_ICMP_SOURCE -s 10.0.0.8/32 -p icmp -j AZURE_ICMP_ACTION -A AZURE_CHECK_ICMP_SOURCE -s 10.0.0.6/32 -p icmp -j AZURE_ICMP_ACTION -A AZURE_CHECK_ICMP_SOURCE -s 10.0.32.6/32 -p icmp -j AZURE_ICMP_ACTION -A AZURE_CHECK_ICMP_SOURCE -s 10.0.0.5/32 -p icmp -j AZURE_ICMP_ACTION -A AZURE_CHECK_ICMP_SOURCE -s 10.0.32.4/32 -p icmp -j AZURE_ICMP_ACTION -A AZURE_CHECK_ICMP_SOURCE -s 10.0.32.5/32 -p icmp -j AZURE_ICMP_ACTION -A AZURE_ICMP_ACTION -j LOG -A AZURE_ICMP_ACTION -j DROP
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 (OpenShift Container Platform 4.6.52 bug fix 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-2021:5010