Bug 1516589
| Summary: | 'oadm diagnostics NetworkCheck' will always using 'registry.access.redhat.com' pull images | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
| Component: | Networking | Assignee: | Ravi Sankar <rpenta> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Meng Bo <bmeng> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.7.0 | CC: | aos-bugs, dapark, smunilla, weliang |
| Target Milestone: | --- | ||
| Target Release: | 3.9.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | v3.9.0-0.19.0 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: incorrect registry path was used by network diagnostics
Consequence: image pull fails
Fix: Fix registry path used by network diags
Result: image pull succeeds
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-18 18:08:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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
...
|
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: