Problem description: Not able to startup diagnostics container with latest deployer image with below error message: [Note] Running diagnostic: DiagnosticPod Description: Create a pod to run diagnostics from the application standpoint Info: Output from the diagnostic pod (image openshift/origin-deployer:latest): Pod "pod-diagnostic-test-zob7e" in namespace "default" : pod is not in 'Running', 'Succeeded' or 'Failed' state - State: "Pending" Origin/Image M M Regression testBlocker Version-Release number of selected component (if applicable): Diagnostics pod image used for Origin: openshift/origin-deployer latest e3e264f29e61 5 hours ago 513.8 MB docker.io/openshift/origin-deployer v1.1.2 79e64c334a5f 10 days ago 499.9 MB Diagnostics pod image used for OSE: rcm-img-docker01.build.eng.bos.redhat.com:5001/openshift3/ose-deployer v3.1.1.902 45a124d31546 13 hours ago 459.2 MB Steps to Reproduce: 1.Login openshift master machine, run "openshift ex diagnostics" 2.Or alternatively run "openshift ex diagnostics" from oc client as an ordinary user Actual Result: Not able to startup diagnostics container with latest deployer images: [Note] Running diagnostic: DiagnosticPod Description: Create a pod to run diagnostics from the application standpoint Info: Output from the diagnostic pod (image openshift/origin-deployer:latest): Pod "pod-diagnostic-test-zob7e" in namespace "default" : pod is not in 'Running', 'Succeeded' or 'Failed' state - State: "Pending" Expected Result: Should be able to startup diagnostics container succesfully
This is due to issue https://github.com/openshift/origin/issues/7358 where the kubelet returns errors as logs.
This appears to be fixed as of latest rebase in Origin.
Verified on origin with devenv-rhel7_3505, issue is fixed. Diagnostics pod can start up now.