Description of problem: While investigating an outage of `etcd` in OpenShift Container Platform 4.7.28 the following messages were found. > Sep 13 05:02:21 master02.example.com crio[1679]: 2021/09/13 05:01:57 http: superfluous response.WriteHeader call from github.com/cri-o/cri-o/server.(*Server).GetInfoMux.func3 (inspect.go:157) > Sep 13 05:02:54 master02.example.com crio[1679]: 2021/09/13 05:02:53 http: superfluous response.WriteHeader call from github.com/cri-o/cri-o/server.(*Server).GetInfoMux.func3 (inspect.go:157) It's not clear what happen and whether those are related to the `etcd` outage. But it would be nice to further investigate that messages as it seems `cri-o` was not working as expected and we need to understand the reason for this. Version-Release number of selected component (if applicable): - OpenShift Container Platform 4.7.28 - cri-o-1.20.4-14.rhaos4.7.gitbce257b.el8.x86_64 How reproducible: - N/A Steps to Reproduce: 1. N/A Actual results: It's not clear whether the messages above indicate that `cri-o` was misbehaving or if that is related to the problem OpenShift Container Platform was having. Expected results: No such message being reported by `cri-o` or at least with better explaining of what was/is happening. Additional info:
Confirmed, a fix is incoming in https://github.com/cri-o/cri-o/pull/5405. Since the issue does not seem critical I'd like to avoid a backport and just resolve it on the main branch.
PR got merged, the latest CRI-O master does contain the fix.
I didn't get similar error from crio during last 14 days by https://search.ci.openshift.org/?search=superfluous+response.WriteHeader+call&maxAge=168h&context=1&type=all&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job.
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 (OpenShift Container Platform 4.7.44 bug fix update), 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-2022:0647