Bug 2090838 - Flaky test: ignore flapping host interface 'tunbr'
Summary: Flaky test: ignore flapping host interface 'tunbr'
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Joao Marcal
QA Contact: Tai Gao
Brian Burt
Depends On:
TreeView+ depends on / blocked
Reported: 2022-05-26 16:33 UTC by Dan Williams
Modified: 2022-08-10 11:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Before this update, the "tunbr" interface caused the alert NodeNetworkInterfaceFlapping to be triggered however, this interface is an ephemeral (eg, virtual) interface much like veths. With this update, we added "tunbr" to the list of interfaces o be ignored which resolves the issue.
Clone Of:
Last Closed: 2022-08-10 11:14:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1681 0 None open Bug 2090838: ignore flapping host interface 'tunbr' 2022-05-31 14:47:33 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:15:00 UTC

Description Dan Williams 2022-05-26 16:33:03 UTC
{  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.

Comment 3 Tai Gao 2022-06-06 02:05:53 UTC

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

Comment 7 errata-xmlrpc 2022-08-10 11:14:36 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.