Customer Contact Name:
Description of Problem:
IPI failed due to image pull failure.
This is because startironic.sh starts the image-customization container with sudo which causes the loss of proxy env.
This problem can be resolved by simply removing the sudo used in startironic.sh because this script is executed under the root user.
Version-Release number of selected component:
This issue was detected in the Pre-GA version.
Red Hat OpenShift Container Platform Version Number: 4.10
Release Number: 4.10.0-0.nightly-2021-12-20-231053
Kubernetes Version: 1.22.1
Cri-o Version: 1.23.0
Related Component: NONE
Related Middleware/Application: irmc
Underlying RHCOS Release Number: 4.10
Underlying RHCOS Architecture: x86_64
Underlying RHCOS Kernel Version: 4.18.0
Drivers or hardware or architecture dependency:
Step to Reproduce:
$ openshift-install --dir ~/clusterconfigs create manifests
$ openshift-install --dir ~/clusterconfigs --log-level debug create cluster
IPI fails due to image pull failure
Image can be pulled normally
Summary of actions taken to resolve issue:
Fujitsu sent PR: https://github.com/openshift/installer/pull/5513
Location of diagnostic data:
Model: RX2540 M4
Hi, in order to properly verify the bug I would like to get more information about the environment and content of proxy section in install-config.yaml, in my test env with squid proxy I wasn't able to reproduce the original issue
Hase-San- would you or one of your colleagues be able to provide the information requested in https://bugzilla.redhat.com/show_bug.cgi?id=2039109#c3 to our QE Team? Thank you.
Dear Victor, Jacob,
I share proxy setting in install-config.yaml
We use local address in install-config.yaml, but we forward the proxy(we use an external proxy actually).
192.168.30.Z is bastion machine of our environment, and this bastion forwards proxy to external.
Created attachment 1851837 [details]
Proxy setting in install-config.yaml
Thank you Futakawa-san.
Dear Victor, Jacob,
Fujitsu confirmed that we could download the image correctly with the latest nightly which contains PR5513.
So this BZ is fixed.
Following customer comment, the bug was verified
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 (Moderate: OpenShift Container Platform 4.10.3 security 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.