-
Bug
-
Resolution: Unresolved
-
Major
-
ACM 2.13.0
-
2
-
False
-
-
False
-
-
-
ACM Console Train 33 - 1
-
None
Description of problem:
console-mce pods are in CrashLoopBackOff due to readiness and liveness probe failure.
Version-Release number of selected component (if applicable):
2.13
Additional info:
We increased the timeout seconds for console-mce-console deployment to 10 seconds and that resolved their issue but after 1 or 2 days, changes got reverted back and timeoutSeconds were changed back to 5 seconds
containers:
- env:
livenessProbe:
failureThreshold: 3
httpGet:
path: /livenessProbe
port: 3000
scheme: HTTPS
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 5. <--
name: console
ports:
- containerPort: 3000
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /readinessProbe
port: 3000
scheme: HTTPS
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 5. <---
Impact :-
timeoutSeconds is not increasing which is causing performance issues and its needs to increased so that pods can schedule seamlessly.
