Description of problem:
we can see sometimes this error:
I0902 10:31:51.476431 22783 prober.go:111] Readiness probe for "logging-es-xxxxxxxx-NN-yyyyy_logging(......):elasticsearch" failed (failure): cat: /opt/app-root/src/init_failures: No such file or directory
in fact, the readiness, at the end, does this check:
check_for_init_complete || cat ${HOME}/init_failures
But it could be possible that init.sh has not yet generated the file "${HOME}/init_complete" even if there are no errors yet, so, ${HOME}/init_failures is empty or non-existent as in this case.
We should take care of this situation and avoid the
cat: /opt/app-root/src/init_failures: No such file or directory
Version-Release number of selected component (if applicable): atomic-openshift-3.11.98-1.git.0.0cbaff3.el7.x86_64
How reproducible: at customer site.
Steps to Reproduce:
1. I guess we could put a "sleep X" in init.sh to force this message.
Comment 3Greg Rodriguez II
2019-10-28 19:47:23 UTC
Added another customer experiencing this issue. Is there a known workaround that has been developed?
(In reply to Greg Rodriguez II from comment #4)
> Customer states this affecting production and would like any type of
> workaround or resolution
Delete the readiness probe from the Deployment. You may have to manually seed the permissions 'oc exec -c elasticsearch -- es_seed_acl'
Comment 8Greg Rodriguez II
2019-11-08 20:21:36 UTC
Customer is requesting update on this ticket. Has there been any progress?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:0062
Description of problem: we can see sometimes this error: I0902 10:31:51.476431 22783 prober.go:111] Readiness probe for "logging-es-xxxxxxxx-NN-yyyyy_logging(......):elasticsearch" failed (failure): cat: /opt/app-root/src/init_failures: No such file or directory in fact, the readiness, at the end, does this check: check_for_init_complete || cat ${HOME}/init_failures But it could be possible that init.sh has not yet generated the file "${HOME}/init_complete" even if there are no errors yet, so, ${HOME}/init_failures is empty or non-existent as in this case. We should take care of this situation and avoid the cat: /opt/app-root/src/init_failures: No such file or directory Version-Release number of selected component (if applicable): atomic-openshift-3.11.98-1.git.0.0cbaff3.el7.x86_64 How reproducible: at customer site. Steps to Reproduce: 1. I guess we could put a "sleep X" in init.sh to force this message.