Loading...

XML

Word

Printable

Type: Bug
Resolution: Done-Errata
Priority: Blocker
Fix Version/s: OADP 1.5.0
Affects Version/s: None
Component/s: operator
Labels:

Activity Type:
Quality / Stability / Reliability
Story Points:
3
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Fixed in Build:
oadp-operator-bundle-container-1.5.0-3
QEStatus:
ToDo
Intelligence Requested:
Market:

WSJF:
0
Risk Probability:
Very Likely
Risk Score:
0

Workstream:

None

Root Cause:
Unset
Failure Category:
Unknown

Regression:
None

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

Description of problem:

Ensure containers are all using FallbackToLogsOnError in terminationMessagePolicy

https://github.com/redhat-best-practices-for-k8s/certsuite

https://kubernetes.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/#:~:text=Moreover%2C%20users%20can%20set%20the,80%20lines%2C%20whichever%20is%20smaller.

links to

openshift/oadp-operator#1590: Fix OADP-5183: Ensure containers are all using FallbackToLogsOnError in terminationMessagePolicy

RHEA-2025:145537 OpenShift API for Data Protection (OADP) 1.5

1.	[RedHat QE] Verify Bug OADP-5183 - Operator best practices #31: Ensure containers are all using FallbackToLogsOnError in terminationMessagePolicy		Closed		Amos Mastbaum
2.	[IBM QE-P] Verify Bug OADP-5183 - Operator best practices #31: Ensure containers are all using FallbackToLogsOnError in terminationMessagePolicy		Closed		Aniruddha Nayek
3.	[IBM QE-Z] Verify Bug OADP-5183 - Operator best practices #31: Ensure containers are all using FallbackToLogsOnError in terminationMessagePolicy		Closed		Ukthi Prasad

Assignee:: Shubham Pampattiwar

Reporter:: Wes Hayutin

QA Contact:: Amos Mastbaum

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/11/06 8:43 PM

Updated:: 2025/08/08 9:10 PM

Resolved:: 2025/06/10 2:03 PM