Description of problem: When I setup the env, its using 'registry.reg-aws.openshift.com:443' as the default registry. but `oadm diagnostics NetworkCheck` will always using 'registry.access.redhat.com'. thus we must give the correct the registry by updating --network-pod-image and --network-test-pod-image when run `oadm diagnostics NetworkCheck'. I'm not sure if the 'registry.access.redhat.com' is hardcode when building or can be config in some place. you can see in: # oadm diagnostics NetworkCheck --help --master-config='': Path to master config file (implies --host) --network-logdir='/tmp/openshift/': Path to store network diagnostic results in case of errors --network-pod-image='registry.access.redhat.com/openshift3/ose:v3.7.9': Image to use for network diagnostic pod --network-test-pod-image='registry.access.redhat.com/openshift3/ose-deployer:v3.7.9': Image to use for network diagnostic test pod this issue happen 3.5/3.6/3.7, see bug https://bugzilla.redhat.com/show_bug.cgi?id=1505898#c6-c12 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: see $description Expected results: the registry can be set not hardcode 'registry.access.redhat.com' 'oadm diagnostics NetworkCheck' can pull image using correct registry automatically without provide the options Additional info:
Fixed by https://github.com/openshift/origin/pull/17315
Verified this bug on v3.9.0-0.19.0 oc adm diagnostics NetworkCheck --help ... ... --network-pod-image='openshift3/ose:v3.9.0-0.19.0': Image to use for network diagnostic pod --network-test-pod-image='openshift3/ose-deployer:v3.9.0-0.19.0': Image to use for network diagnostic test pod ...