Description of problem:
In an environment where we need the proxy to download the RHCOS images we are hitting the following issues:
1. We have a proxy configured in the install-config.yaml.
2. The coreos-downloader container running on the Bootstrap VM is able to pull the RHCOS images.
3. Once the cluster is deployed, the metal3 pod fails to initialize. The container metal3-machine-os-downloader cannot pull the RHCOS images.
It seems that the metal3 deployment is not consuming the cluster-wide proxy configuration.
We tried to rsh into the container and as expected, when setting the https proxy everything works as expected:
sh-4.4# curl https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/latest/latest/rhcos-4.6.8-x86_64-openstack.x86_64.qcow2.gz
sh-4.4#
sh-4.4#
sh-4.4# https_proxy=http://192.168.1.10:3128 curl https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/latest/latest/rhcos-4.6.8-x86_64-openstack.x86_64.qcow2.gz -O
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 844M 0 864k 0 0 850k 0 0:16:57 0:00:01 0:16:56 849k^C
Version-Release number of selected component (if applicable):
4.6.8
How reproducible:
Always
Steps to Reproduce:
Stated in the description
Actual results:
Metal3 pod fails to initialize
Expected results:
Metal3 pod initializes
Additional info:
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.6.29 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.
https://access.redhat.com/errata/RHBA-2021:1521