-
Bug
-
Resolution: Done
-
Undefined
-
4.10
-
None
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-5559. The following is the description of the original issue:
—
Description of problem:
Azure VIP 168.63.129.16 needs to be noProxy to let a VM report back about it's creation status [1]. A similar thing needs to be done for the armEndpoint of ASH - to make sure that future cluster nodes do not communicate with a Stack Hub API through proxy [1] https://docs.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16
Version-Release number of selected component (if applicable):
4.10.20
How reproducible:
Need to have a proxy server in ASH and run the installer
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected these two be auto-added as they are very specific and difficult to troubleshoot
Expected results:
Additional info:
This is a clone of https://bugzilla.redhat.com/show_bug.cgi?id=2104997 against the cluster-network-operator since the fix involves changing both the operator and the installer.
- clones
-
OCPBUGS-5559 add default noProxy config for Azure
- Closed
- is blocked by
-
OCPBUGS-5559 add default noProxy config for Azure
- Closed
- is duplicated by
-
OCPBUGS-9371 Automatically add 168.63.129.16 IP to noProxy in Azure Stack Hub
- Closed
- links to