Description of problem: [Hypershift] EgressIP doesn't work in hypershift guest cluster Version-Release number of selected component (if applicable): 4.11.0-0.nightly-2022-05-20-213928 How reproducible: Always Steps to Reproduce: $ oc get nodes NAME STATUS ROLES AGE VERSION ip-10-0-133-27.us-east-2.compute.internal Ready worker 23h v1.23.3+ad897c4 ip-10-0-135-234.us-east-2.compute.internal Ready worker 23h v1.23.3+ad897c4 ip-10-0-141-144.us-east-2.compute.internal Ready worker 23h v1.23.3+ad897c4 $ oc label node ip-10-0-133-27.us-east-2.compute.internal k8s.ovn.org/egress-assignable= node/ip-10-0-133-27.us-east-2.compute.internal labeled $ oc get egressip NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS egressip-2 10.0.133.101 $ oc get event | grep egressip 6m8s Warning NoMatchingNodeFound egressip/egressip-2 no assignable nodes for EgressIP: egressip-2, please tag at least one node with label: k8s.ovn.org/egress-assignable Actual results: EgressIP wasn't assinged to egress nodes. Expected results: EgressIP works normally Additional info: Some comments from DEV: egress IP doesn't work in hypershift because ovn-k master checks if egress nodes are reachable by opening a connection to nodes management IP. However master cannot reach node in hypershift
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069