Red Hat Bugzilla – Bug 1475680
DiagnosticPod can't run due to image name wrongly interpreted
Last modified: 2018-01-15 13:12:43 EST
Description of problem:
DiagnosticPod can't run on OCP 3.6.0 since image repo not correctly set, the current cli attempted to use:
Version-Release number of selected component (if applicable):
# openshift version
Steps to Reproduce:
1.login openshift master, run "oadm diagnostics DiagnosticPod"
# oadm diagnostics DiagnosticPod
[Note] Determining if client configuration exists for client/cluster diagnostics
Info: Successfully read a client config file at '/root/.kube/config'
[Note] Running diagnostic: DiagnosticPod
Description: Create a pod to run diagnostics from the application standpoint
WARN: [DCli2006 from diagnostic DiagnosticPod@openshift/origin/pkg/diagnostics/client/run_diagnostics_pod.go:135]
Timed out preparing diagnostic pod logs for streaming, so this diagnostic cannot run.
It is likely that the image 'registry.access.redhat.com/openshift3/ose-deployer:v3.6.171' was not pulled and running yet.
Last error: (*errors.StatusError) container "pod-diagnostics" in pod "pod-diagnostic-test-r05ht" is waiting to start: image can't be pulled
[Note] Summary of diagnostics execution (version v3.6.171):
[Note] Warnings seen: 1
Diag pod should run with this image:
You can use --images to set the correct image template string. For instance this ought to work:
oadm diagnostics DiagnosticPod --images=openshift3/ose-deployer:v3.6.171
At least, assuming that image is available (should check w/ docker pull on a node). The tag, BTW, comes from the client, which has no knowledge of what the server uses or has access to. I'm not sure where it's getting the registry from here, will have to revisit how that works. Still, this shouldn't block testing or the eventual use when this is released.
The same solution applies for the network diagnostic.
Just cleaning up an old bug here. It seems to be working as designed, but feel free to reopen and explain if you believe otherwise.