It was discovered that healthchecks aren't really reliable because they
aren't strict enough.
The current patch adds the "standard" options in order to ensure we
actually catch errors soon enough in order to return the actual state of
the checked element.
It also requires a small change for the healthcheck_port() function,
since the "piping" returned a 141 code instead of 0 due SIGPIPE being
sent at some point[1].
Reviewed: https:/ /review. opendev. org/708304 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=5a1f5dbdd18 712183d44955e91 25ff9a805ca97f
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit 5a1f5dbdd187121 83d44955e9125ff 9a805ca97f
Author: Cédric Jeanneret <email address hidden>
Date: Wed Jan 22 16:23:24 2020 +0100
Make healthchecks more strict
It was discovered that healthchecks aren't really reliable because they
aren't strict enough.
The current patch adds the "standard" options in order to ensure we
actually catch errors soon enough in order to return the actual state of
the checked element.
It also requires a small change for the healthcheck_port() function,
since the "piping" returned a 141 code instead of 0 due SIGPIPE being
sent at some point[1].
[1] https:/ /stackoverflow. com/questions/ 19120263/ why-exit- code-141- with-grep- q www.tldp. org/LDP/ lpg/node20. html
http://
Change-Id: If13b6ca177d47a 0af29ba5e5099e0 40eea62876c /bugzilla. redhat. com/show_ bug.cgi? id=1794044 f4f11d99bf7ce8f 5bb89744e7)
Closes-Bug: #1860556
Related: https:/
(cherry picked from commit 475368e9b7b6175