Bug 1309193

Summary: [Intservice_public_88] Diagnostics container failed to start up with latest deployer image
Product: OKD Reporter: Xia Zhao <xiazhao>
Component: ocAssignee: Luke Meyer <lmeyer>
Status: CLOSED CURRENTRELEASE QA Contact: Wei Sun <wsun>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, lmeyer, mmccomas
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 17:09:19 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:
Bug Depends On:    
Bug Blocks: 1302649    

Description Xia Zhao 2016-02-17 07:06:41 UTC
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

Comment 1 Luke Meyer 2016-02-17 16:06:18 UTC
This is due to issue https://github.com/openshift/origin/issues/7358 where the kubelet returns errors as logs.

Comment 2 Luke Meyer 2016-02-19 16:40:26 UTC
This appears to be fixed as of latest rebase in Origin.

Comment 3 Xia Zhao 2016-02-22 07:32:59 UTC
Verified on origin with devenv-rhel7_3505, issue is fixed. Diagnostics pod can start up now.