oc-diagnostics.log

[Note] Determining if client configuration exists for client/cluster diagnostics
Info:  Successfully read a client config file at '/home/stenvix/.kube/config'
[Note] Could not configure a client with cluster-admin permissions for the current server, so cluster diagnostics will be skipped

[Note] Running diagnostic: ConfigContexts[schedule/api-starter-us-west-2-openshift-com:443/[email protected]]
       Description: Validate client config context is complete and has connectivity

Info:  For client config context 'schedule/api-starter-us-west-2-openshift-com:443/[email protected]':
       The server URL is 'https://api.starter-us-west-2.openshift.com:443'
       The user authentication is '[email protected]/api-starter-us-west-2-openshift-com:443'
       The current project is 'schedule'
       Successfully requested project list; has access to project(s):
         [uschedule]

[Note] Running diagnostic: DiagnosticPod
       Description: Create a pod to run diagnostics from the application standpoint

WARN:  [DCli2006 from diagnostic DiagnosticPod@openshift/origin/pkg/oc/admin/diagnostics/diagnostics/client/pod/run_diagnostics_pod.go:173]
       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.10.9' was not pulled and running yet.
       Last error: (*errors.StatusError[2]) container "pod-diagnostics" in pod "pod-diagnostic-test-f2cbc" is waiting to start: image can't be pulled

[Note] Summary of diagnostics execution (version v3.10.9):
[Note] Warnings seen: 1