-
Bug
-
Resolution: Unresolved
-
Major
-
ACM 2.13.0
-
0
-
False
-
-
False
-
-
-
ACM Console Train 33 - 2
-
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. <---
Need for this :- While restarting the pod, since timeoutSecond is low, pod is continuously failing with probe failure error and customizing timeSecond is not an option here.
- clones
-
ACM-24964 console-mce pod CrashLoopBackOff due to probe failure - increase timeouts [release-2.14]
-
- Closed
-