+++ This bug was initially created as a clone of Bug #1918879 +++
--- Additional comment from Gabe Montero on 2021-01-22 16:08:14 UTC ---
For testing this XiuJuan import a pull secret and then edit it so you corrupt/break the encoded value associated with the.dockerconfigjson key so we cannot json unmarshal it
log.V(0).Infof("error trying to parse file %s: %s", filePath, err.Error())
should show up in the build log
and the error
fmt.Errorf("%s; also, error processing dockerconfigjson: %s", err.Error(), dockerConfigCredsErr.Error())
should be propagated up and ultimately visible from the log
the bonus scenario is to do this with a build pull secret, but the registry handled by that pull secret can also be handled by the node credentials (I *think* registry.redhat.io is such a registry).
you should see the log log.V(0).Infof("error trying to parse file %s: %s", filePath, err.Error()) still, but presumably the build could still work since the pull is authenticated via the node credentials instead of the supply pull secret
4.6 PR https://github.com/openshift/builder/pull/210 is waiting QE verification on https://github.com/openshift/builder/pull/200
Test on cluster building from pr openshift/builder#210, the version '4.6.0-0.ci.test-2021-02-08-034130-ci-ln-6w1gdyt'
Could see the error from build logs with invalid pullsecret.
"error trying to parse file /var/run/secrets/openshift.io/pull/.dockerconfigjson: illegal base64 data at input byte 3"
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.18 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.