[jboss-jira] [JBoss JIRA] (WFWIP-176) Pod restarted because of failing liveness/rediness Probe
[
https://issues.jboss.org/browse/WFWIP-176?page=com.atlassian.jira.plugin....
]
Martin Choma commented on WFWIP-176:
------------------------------------
[~luck3y] I have realized we are porbably missing in eap73 (is it correct branch [1]?)
commit differenciating behaviour of livenessProbe.sh on OCP 4 [1]
I want to make sure it is intentional and not forgotten by mistake. As I understand new
behaviour is correct one. And fixing old incorrect behaviour.
But at least we should document that change in release notes, wdyt?
[1] https://github.com/jboss-container-images/jboss-eap-modules/commits/master
[2]
https://github.com/jboss-container-images/jboss-eap-modules/commit/f03323...
Pod restarted because of failing liveness/rediness Probe
--------------------------------------------------------
Key: WFWIP-176
URL: https://issues.jboss.org/browse/WFWIP-176
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Ken Wills
Priority: Major
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
{code}
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
{code}
and CD 17 case
{code}
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
{code}
What could cause this behaviour change?
[0] https://issues.jboss.org/browse/CLOUD-1988
--
This message was sent by Atlassian Jira
(v7.12.1#712002)