-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Documentation (Ref Guide, User Guide, etc.)
During testing 73 image I came to case where really corner case is tested [0].
Test is not using templates for deployment.
In tested scenario liveness/readiness probe fails. In CD 17 and eap 73 pod is restarted. In CD 16 however, there was no liveness/rediness failures in events. Pod was not restarted.
I dont see differences in pod yaml for CD16 case
livenessProbe:
exec:
command:
- /bin/bash
- '-c'
- /opt/eap/bin/livenessProbe.sh
failureThreshold: 3
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: weirdusername
readinessProbe:
exec:
command:
- /bin/bash
- '-c'
- /opt/eap/bin/readinessProbe.sh
failureThreshold: 3
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
and CD 17 case
livenessProbe:
exec:
command:
- /bin/bash
- '-c'
- /opt/eap/bin/livenessProbe.sh
failureThreshold: 3
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: weirdusername
readinessProbe:
exec:
command:
- /bin/bash
- '-c'
- /opt/eap/bin/readinessProbe.sh
failureThreshold: 3
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
What could cause this behaviour change?
- duplicates
-
JBEAP-17528 [Doc 7.3.0.Beta] changes to liveness/readiness probes when migrating to EAP 7.3 images
-
- Closed
-