Upgraded a 3.10 cluster to 3.11, started seeing: I0725 01:32:00.248336 1 healthz.go:72] /healthz/log check I0725 01:32:00.375613 1 healthz.go:72] /healthz/log check I0725 01:32:01.314116 1 healthz.go:72] /healthz/log check I0725 01:32:01.314499 1 healthz.go:72] /healthz/log check I0725 01:32:01.352899 1 healthz.go:72] /healthz/log check I0725 01:32:01.958673 1 healthz.go:72] /healthz/log check I0725 01:32:02.088116 1 healthz.go:72] /healthz/log check I0725 01:32:02.527264 1 healthz.go:72] /healthz/log check I0725 01:32:02.777314 1 healthz.go:72] /healthz/log check I0725 01:32:03.122310 1 healthz.go:72] /healthz/log check I0725 01:32:04.490906 1 healthz.go:72] /healthz/log check I0725 01:32:04.753904 1 healthz.go:72] /healthz/log check I0725 01:32:05.249579 1 healthz.go:72] /healthz/log check I0725 01:32:05.376440 1 healthz.go:72] /healthz/log check I0725 01:32:06.315330 1 healthz.go:72] /healthz/log check I0725 01:32:06.315330 1 healthz.go:72] /healthz/log check I0725 01:32:06.959980 1 healthz.go:72] /healthz/log check I0725 01:32:07.096326 1 healthz.go:72] /healthz/log check Not sure what this message is supposed to be, but I don't have a high log level set.
Fix:
Fix: https://github.com/openshift/origin/pull/20616
Checked in openshift v3.11.0-0.14.0 env, it reproduces the log spam. In openshift v3.11.0-0.16.0 env, no that issue, verified.
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-2018:2652