Description of problem:

The AWS metadata endpoint is unreachable after removing a Windows node from an ovn-hybrid cluster. This seems to only occur on newer AMIs. Most likely related to a recent release of EC2LaunchV2 https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launchv2-versions.html

Version-Release number of selected component (if applicable):

How reproducible:

Always

Steps to Reproduce:

1. Add a BYOH Windows node https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/windows_container_support_for_openshift/byoh-windows-instance

2. Remove the node from the cluster by deleting its entry in the BYOH configmap, or by deleting the configmap:

oc delete cm -n openshift-windows-machine-config-operator windows-instances

3. Access the VM and check if AWS metadata endpoint is reachable

Actual results:
The endpoint is unreachable

Expected results:
The endpoint is reachable and the API is usable

Additional info:

Affected Platforms:
AWS

Hybrid overlay code: https://github.com/ovn-kubernetes/ovn-kubernetes/tree/master/go-controller/hybrid-overlay