{ fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Apr 27 16:54:36.652: Unexpected alerts fired or pending after the test run: alert NodeNetworkInterfaceFlapping fired for 30 seconds with labels: {container="kube-rbac-proxy", device="tunbr", endpoint="https", instance="ci-op-4tkrp5cf-5cb9e-bcvll-worker-westus-wh5w6", job="node-exporter", namespace="openshift-monitoring", pod="node-exporter-hqx9n", service="node-exporter", severity="warning"}} tunbr is an ephemeral (eg, virtual) interface much like veths. It's not a node NIC and should be ignored.
release: 4.11.0-0.nightly-2022-06-04-014713 test process: 1.Open admin console, navigate to Observe->Alerting, then click "Alerting rules" in the page 2.In-put "NodeNetworkInterfaceFlapping" in the search box, then click the matched alerting rule 3.Expression displayed as: changes(node_network_up{device!~"veth.+|tunbr",job="node-exporter"}[2m]) > 2 The result is consistent with the modification of PR code change, test passed
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069