Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
job link
the test failure junit output is just this:
{ fail [github.com/onsi/ginkgo@v4.7.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"}}
link to this job's testgrid for reference.
This failure seems pretty infrequent and search.ci (as of 4/28/2022) only has it showing up in .43% of all failures in ovn jobs. What stood out to me was the alert started
firing toward the end of the e2e tests and not in the early stages just after the cluster install is done.
Attachments
Issue Links
- clones
-
-
- Closed
-
- links to