-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
ACM 2.12.0, ACM 2.10.4, ACM 2.11.2, MCE 2.5.5
-
None
Description of problem:
search-postgres gets OOMKILLEd by ocp
Version-Release number of selected component (if applicable):
2.10.4
2.5.5
How reproducible:
Customer environment
Steps to Reproduce:
- deploy RHACM and attach 46 ocp clusters
- configure search
Actual results:
search-postgres gets oomkilled, logs are not readable
Expected results:
search-postgres doesn't get oomkilled or we have a clearer reason for the oomkilled status
Additional info:
- the ressource limit that is found to affect search-postgres is not documented
- the logs of search-postgres in the must-gather seem to not have been available
- some of the search-postgres instances are in "ContainerUnknownStatus"
- causes
-
ACM-12208 Upgrading ACM causes search-postgres pod to be in CrashLoopBackOff state
-
- Resolved
-
- links to