Bug 2104997 - Automatically add 168.63.129.16 IP to noProxy in Azure Stack Hub
Summary: Automatically add 168.63.129.16 IP to noProxy in Azure Stack Hub
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 4.12.z
Assignee: Brent Barbachem
QA Contact: Mike Gahagan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-07 16:36 UTC by Arseni
Modified: 2023-11-15 00:37 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2023-03-09 01:23:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 6374 0 None open Bug 2104997: Add additional fields to proxy manifest 2022-09-19 18:16:41 UTC

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


Note You need to log in before you can comment on or make changes to this bug.