Closed remiblondel closed 1 year ago
After some additional troubleshooting, I found out that proxy settings on master nodes are not set through the ignition script (which creates a proxy.sh file) like for the bootstrap node.
Proxy configuration on master nodes directly depends on the cluster-proxy-01-config.yaml
file generated after launching openshift-install create manifests
command.
This file was accidentaly overwritten at some point (the proxy settings were deleted), leading the proxy configuration not to be applied.
Version
Platform:
aws
IPI
Initial configuration
Proxy section in my install-config.yaml file looks like this:
The problem
Proxy configuration was nowhere to be found on master nodes even though I see it on the bootstrap node when I do:
env | grep proxy
This leads the master nodes to fail pulling images on quay.io:
Additional Info
Flow from the master nodes to the proxy is open:
-> Returns "True"
Proxy configuration was nowhere to be found on master nodes even though I see it on the bootstrap node when I do:
env | grep proxy
Also, I can see those lines in the bootstrap node logs but not in the master nodes:
(proxy.sh file exports the proxy settings I put in the install-config.yaml file).
Followed documentation
https://docs.openshift.com/container-platform/4.11/installing/installing_aws/installing-restricted-networks-aws-installer-provisioned.html#installation-configure-proxy_installing-restricted-networks-aws-installer-provisioned