Bug 1475680 - DiagnosticPod can't run due to image name wrongly interpreted
DiagnosticPod can't run due to image name wrongly interpreted
Status: CLOSED NOTABUG
Product: OpenShift Container Platform
Classification: Red Hat
Component: Command Line Interface (Show other bugs)
3.6.0
Unspecified Unspecified
low Severity low
: ---
: 3.7.0
Assigned To: Luke Meyer
Xia Zhao
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-27 03:24 EDT by Xia Zhao
Modified: 2018-01-15 13:12 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-01-15 13:12:43 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Xia Zhao 2017-07-27 03:24:36 EDT
Description of problem:
DiagnosticPod can't run on OCP 3.6.0 since image repo not correctly set, the current cli attempted to use:
registry.access.../openshift3/ose-deployer:v3.6.171
should use:
brew.../openshift3/ose-deployer:v3.6.171

Version-Release number of selected component (if applicable):
# openshift version
openshift v3.6.171
kubernetes v1.6.1+5115d708d7
etcd 3.2.1

How reproducible:
always

Steps to Reproduce:
1.login openshift master, run "oadm diagnostics DiagnosticPod"
2.
3.

Actual results:
# 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[2]) 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


Expected results:
Diag pod should run with this image:
brew.../openshift3/ose-deployer:v3.6.171

Additional info:
Comment 1 Luke Meyer 2017-07-27 14:06:52 EDT
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.
Comment 3 Luke Meyer 2018-01-15 13:12:43 EST
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.

Note You need to log in before you can comment on or make changes to this bug.