Description of problem:
I have a customer having issues with the noproxy settings:
We have to pull the container images via a proxy. I've configured it like below:
Currently I have to specify every single ip address to be excluded from the proxy. I would rather use 10.118.17.0/26 in the noProxy config but unfortunately that does not work.
In the Openshift3 config it was possible to set a subnetrange ( see chapter 23.3. Configuring Hosts for Proxies) : https://access.redhat.com/documentation/en-us/openshift_container_platform/3.4/html/installation_and_configuration/install-config-http-proxies
If i check the bootstrap node it has automatically added some subnet ranges with should be excluded from the proxy but this does not work either:
[root@bootstrap ~]# set | grep -i proxy
Version-Release number of selected component (if applicable):
Openshift 4.8 Baremetal Install
Steps to Reproduce:
Why this component is set to MetalLB ? Metallb is not even exists in 4.8 release ?
I assume u are using openshift-install command to create ur cluster ? I just tried an install-config.yaml using something like the following
- architecture: amd64
and it didn't complain
(In reply to Mohamed Mahmoud from comment #13)
> I assume u are using openshift-install command to create ur cluster ? I just
> tried an install-config.yaml using something like the following
> apiVersion: v1
> baseDomain: gcp.devcluster.openshift.com
> httpProxy: http://10.10.10.11:3128
> httpsProxy: http://10.10,10.11:3128
> noProxy: 10.118.17.0/26,10.118.145.64/26
> - architecture: amd64
> and it didn't complain
were u able to repro this issue if its that straight fwd to repro ?
pls collect the installion logs per https://docs.openshift.com/container-platform/4.8/installing/installing-troubleshooting.html#installation-bootstrap-gather_installing-troubleshooting
and share them
This bug appears to be a duplicate of bz#1990556
A solution is currently being worked on and a workaround is described in bz#1990556
Let us know if this workaround works for your setup
Attaching fix to support CIDR in the RHOS image download container
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.8.25 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.
no need in automation, same issue covered by https://bugzilla.redhat.com/show_bug.cgi?id=1990556