Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
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 sovereign clouds.

Result: Cluster nodes do not communicate with a Sovereign Cloud API through proxy.

Show
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 sovereign clouds. Result: Cluster nodes do not communicate with a Sovereign Cloud API through proxy.
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.13.0

Description of problem:

In https://issues.redhat.com/browse/OCPBUGSM-46450, the VIP was added to noProxy for StackCloud but it should also be added for all national clouds.

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

4.10.20

How reproducible:

always

Steps to Reproduce:

1. Set up a proxy
2. Deploy a cluster in a national cloud using the proxy
3.

Actual results:

Installation fails

Expected results:

Additional info:

The inconsistence was discovered when testing the cluster-network-operator changes https://issues.redhat.com/browse/OCPBUGS-5559

blocks

OCPBUGS-8015 Azure: VIP 168.63.129.16 should be noProxy to all clouds except Public

is cloned by

OCPBUGS-8015 Azure: VIP 168.63.129.16 should be noProxy to all clouds except Public

links to