[ https://issues.jboss.org/browse/WFWIP-176?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-176: ------------------------------------ [~brian.stansberry] It is very likely it is related. But I still does not understand fully. In test configuration is bad, so livenessProbe.sh cant passed. But I still wonder why I cant see failing livenessProbe.sh in events. Seems like response of livenessProbe.sh is not processed by openshift at all. After 6 minutes in events shows up `context deadline exceeded` and after 10 minutes pod is killed by deploy pod. Events from CD16 {code} 11:58:33 AM Normal Killing Killing container with id docker://weirdusername:Need to kill Pod 11:58:32 AM Warning Unhealthy Liveness probe failed: 11:58:32 AM Warning Unhealthy Readiness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: cannot exec a container that has run and stopped 11:58:32 AM Warning Unhealthy Readiness probe failed: 11:54:34 AM Warning Unhealthy Readiness probe errored: rpc error: code = DeadlineExceeded desc = context deadline exceeded 11:54:34 AM Warning Unhealthy Liveness probe errored: rpc error: code = DeadlineExceeded desc = context deadline exceeded 11:48:30 AM Normal Started Started container 11:48:29 AM Normal Created Created container 11:48:29 AM Normal Pulled Successfully pulled image "docker-registry.default.svc:5000/mchoma-xtf-builds/ha-servlet-counter-eap-cd@sha256:7f697f40699251c2d9df69c6622255dde212554ad22d7705842895fee204ffef" 11:48:29 AM Normal Pulling pulling image "docker-registry.default.svc:5000/mchoma-xtf-builds/ha-servlet-counter-eap-cd@sha256:7f697f40699251c2d9df69c6622255dde212554ad22d7705842895fee204ffef" 11:48:11 AM Normal Scheduled Successfully assigned mchoma/weirdusername-1-g5jkk to multinode-nfs-mchoma-001-node-2 {code} User impact is minimal in both cases user is unable to deploy the app so I think we can ignore it. I will just change test behaviour. -- This message was sent by Atlassian Jira (v7.12.1#712002)