Bug 2104997

Summary: Automatically add 168.63.129.16 IP to noProxy in Azure Stack Hub
Product: OpenShift Container Platform Reporter: Arseni <akarshak>
Component: InstallerAssignee: Brent Barbachem <bbarbach>
Installer sub component: openshift-installer QA Contact: Mike Gahagan <mgahagan>
Status: CLOSED DEFERRED Docs Contact:
Severity: high    
Priority: unspecified CC: bbarbach, jima, padillon, rdossant, talessio
Version: 4.10   
Target Milestone: ---   
Target Release: 4.12.z   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The ARM Endpoint was not added to noProxy when a proxy was set so that the status could not be recieved. Consequence: No status was received from the Arm Endpoint. Fix: Add 168.63.129.16 when noProxy used in Azure Stack Hub. Result: Cluster nodes do not communicate with a Stack Hub API through proxy.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-09 01:23:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Arseni 2022-07-07 16:36:29 UTC
Version:

$ openshift-install version
4.10.20

Platform:

Azure Stack Hub

Please specify:
IPI (automated install with `openshift-install`. If you don't know, then it's IPI)



What happened?

When proxy server is in place and http(s)Proxy+noProxy is added to isntall-config.yaml. After manifests are generated additional proxy setting should be auto-appended to proxy configuration .yaml

1. Azure VIP 168.63.129.16
See -> https://docs.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16

this needs to be noProxy to let a VM report back about it's creation status

2. armEndpoint of ASH - to make sure that future cluster nodes do not communicate with a Stack Hub API through proxy


What did you expect to happen?

Expected these two be auto-added as they are very specific and difficult to troubleshoot

How to reproduce it (as minimally and precisely as possible)?

Need to have a proxy server in ASH and rung the installer

Comment 7 Rafael Fonseca 2023-01-10 16:30:04 UTC
I created https://issues.redhat.com/browse/OCPBUGS-5559 to capture the cluster-network-operator work.

Comment 9 Shiftzilla 2023-03-09 01:23:42 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9371