Bug 1762968

Summary: Prometheus container doesn't have terminationMessagePolicy FallbackToLogsOnError
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: MonitoringAssignee: Frederic Branczyk <fbranczy>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1763098 (view as bug list) Environment:
Last Closed: 2020-01-23 11:08:20 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: 1763098    

Description Clayton Coleman 2019-10-17 22:22:19 UTC 
While debugging a 4.2 failure I saw that prometheus had exited with exit code 1 but not reported a message.  While most of the other containers have the correct terminationMessagePolicy, Prometheus is wrong.

We need to fix and backport to 4.2 so we can correctly debug when containers exit on error.
Comment 3 errata-xmlrpc 2020-01-23 11:08:20 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0062