Bug 1515940

Summary: Improve debuggability of Jenkins Kubernetes plugin
Product: OpenShift Container Platform Reporter: Jim Minter <jminter>
Component: RFEAssignee: Adam Kaplan <adam.kaplan>
Status: CLOSED CURRENTRELEASE QA Contact: Wenjing Zheng <wzheng>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: adam.kaplan, aos-bugs, bparees, erich, jokerman, mmccomas, rromerom, sreber, sspeiche
Target Milestone: ---   
Target Release: 3.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-11 18:43:37 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:

Description Jim Minter 2017-11-21 16:29:28 UTC
In a customer issue it was hard to diagnose that a child process in a Jenkins slave running on OpenShift was killed by the OOM killer.  The following items would have helped:

1) Jenkins Kubernetes plugin should cleanly terminate the slave agent when it's done, rather than delete its pod.  This would enable Reason: OOMKilled to be seen on the pod status, as well as giving a chance for a meaningful exit code to be set.

2) The Jenkins Kubernetes plugin should look for Reason: OOMKilled on the pod status after slave agent exits, and clearly log if it is seen.

3) It should be possible to disable automatic pod deletion for debugging purposes, allowing slave logs to be recovered and the pod status to be investigated.

Comment 2 Steve Speicher 2018-01-19 16:30:07 UTC
Added to list of cards to consider for 3.10, not committed.

Comment 3 Steve Speicher 2018-06-12 20:08:36 UTC
Proposed for 3.11, didn't make 3.10

Comment 6 Adam Kaplan 2019-02-11 18:43:37 UTC
Released in 3.11