This is a clone of issue OCPBUGS-27959. The following is the description of the original issue:
—
In a CI run of etcd-operator-e2e I've found the following panic in the operator logs:
E0125 11:04:58.158222 1 health.go:135] health check for member (ip-10-0-85-12.us-west-2.compute.internal) failed: err(context deadline exceeded) panic: send on closed channel goroutine 15608 [running]: github.com/openshift/cluster-etcd-operator/pkg/etcdcli.getMemberHealth.func1() github.com/openshift/cluster-etcd-operator/pkg/etcdcli/health.go:58 +0xd2 created by github.com/openshift/cluster-etcd-operator/pkg/etcdcli.getMemberHealth github.com/openshift/cluster-etcd-operator/pkg/etcdcli/health.go:54 +0x2a5
which unfortunately is an incomplete log file. The operator recovered itself by restarting, we should fix the panic nonetheless.
Job run for reference:
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-etcd-operator/1186/pull-ci-openshift-cluster-etcd-operator-master-e2e-operator/1750466468031500288
- blocks
-
OCPBUGS-30067 [4.14] Panic: send on closed channel
- Closed
- clones
-
OCPBUGS-27959 Panic: send on closed channel
- Closed
- is blocked by
-
OCPBUGS-27959 Panic: send on closed channel
- Closed
- is cloned by
-
OCPBUGS-30067 [4.14] Panic: send on closed channel
- Closed
- links to
-
RHSA-2024:1210 OpenShift Container Platform 4.15.z security update