Bug 2112100

Summary: [hybrid-overlay] AWS EC2 metadata service not available in host's vNIC for Windows
Product: OpenShift Container Platform Reporter: jvaldes
Component: NetworkingAssignee: jvaldes
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: high CC: anusaxen, bbennett, jvaldes, rravaiol
Version: 4.10   
Target Milestone: ---   
Target Release: 4.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2112086 Environment:
Last Closed: 2022-10-12 13:36:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2112086    
Bug Blocks:    

Description jvaldes 2022-07-28 19:45:52 UTC 
+++ This bug was initially created as a clone of Bug #2112086 +++

Description of problem:
AWS EC2 metadata service not available in host's vNIC for Windows after hybrid-overlay is configured and running as a Windows service.

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

How reproducible:
Always

Steps to Reproduce:
1. Spin a 4.10 IPI cluster in AWS
2. Install WMCO from Operator-Hub  with all the requirements
3. Deploy a Windows machineSet with Windows Server 2022
4. SSH into a Windows machine and check for the metadata endpoint is reachable before the machine joins as a worker node.
  4.1 Run the following scripts from an existing linux worker node

```
# query the metadata service to fetch the hostname
ssh -o StrictHostKeyChecking=no -i <key.pem> <username>@<internal_IP> powershell.exe -Command "Invoke-WebRequest -UseBasicParsing http://169.254.169.254/latest/meta-data/hostname" 
```

```
# get network routes and look for 169.254.169.254
ssh -o StrictHostKeyChecking=no -i <key.pem> <username>@<internal_IP> powershell.exe -Command "Get-NetRoute" 
```
where <key.pem> is the private key to SSH into the Windows machine, <username> is the Windows username, and <internal_IP is the internal IP of the Windows machine.

5. Wait for WMCO to start hybrid-overlay as a Windows service

6. SSH into a Windows machine and check again the metadata endpoint


Actual results:
AWS EC2 metadata service is not available in host's vNIC after hybrid-overlay is running as a Windows service.


Expected results:
AWS EC2 metadata service should be available in host's vNIC after hybrid-overlay running as a Windows service.

Additional info:

--- Additional comment from  on 2022-07-28 18:48:44 UTC ---

Upstream PR with the proposed fix: https://github.com/ovn-org/ovn-kubernetes/pull/3074

Downstream merge PR: https://github.com/openshift/ovn-kubernetes/pull/1214
Comment 6 errata-xmlrpc 2022-10-12 13:36:47 UTC 
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.11.8 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-2022:6809