Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
ethmonitor generates "WARNING Interface XXX does not exist" at every monitor operation.
The issue occurs when the interface doesn't have an IP address.
is_interface() in ethmonitor script uses 'ip -a -o inet addr show' command.
The command shows interfaces which have IP addresses.
On the other hand, if the interface belongs to (OVS/Linux) bridge.
The physical/bonding interfaces don't have IP addresses.
To detect the correct interface in that situation, we should backport the following commits into RHEL8.2 and RHEL8.4.
~~~
commit 40d05029ce0b2ad437377cf9a8bcb4c91508fa89
Author: Heitor R. Alves de Siqueira <halves>
Date: Thu Mar 21 16:29:33 2019 -0300
ethmonitor: check if interface exists by link
---
commit c0ac191c73f1a3cf62d54b7ec59992997cca3810
Author: Heitor Alves de Siqueira <halves>
Date: Wed Apr 17 17:16:39 2019 -0300
ethmonitor: fix is_interface() regression
Commit 40d05029ce0b changed is_interface() to list by link instead of
address. We need to adjust the grep filter for the new output format,
else we'll miss interfaces.
---
commit 7f7ca75100a846242ff1510fd9bcf299cd3d00eb
Author: Aleksei Burlakov <aleksei.burlakov>
Date: Mon Oct 26 13:25:45 2020 +0100
ethmonitor: is_interface: RE matches vlan names
Vlan names end not with : but are suffixed with the @devices-name
~~~
Version-Release number of selected component (if applicable):
resource-agents in RHEL8.2 and RHEL8.4.
How reproducible:
Everytime when ethmonitor's monitor operation runs.
Steps to Reproduce:
1. Configure an interface which belongs to ovs-bridge.
2. Setup ethmonitor for the bonding device which doesn't have an IP address.
3. Observe the error message is shown.
Actual results:
The warning message is shown
Expected results:
The warning message is not shown.
Additional info:
The message makes user confused. We should prevent it.
Hi Oyvind,
I'm sorry for interrupting you. Do you have any updates on this?
It'll be great if we can backport it into RHEL8.2 and RHEL8.4 which are used with OSP16.x.
Best Regards,
Keigo Noha
Comment 4Oyvind Albrigtsen
2023-03-15 12:22:07 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 (resource-agents bug fix and enhancement 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-2023:6899
Description of problem: ethmonitor generates "WARNING Interface XXX does not exist" at every monitor operation. The issue occurs when the interface doesn't have an IP address. is_interface() in ethmonitor script uses 'ip -a -o inet addr show' command. The command shows interfaces which have IP addresses. On the other hand, if the interface belongs to (OVS/Linux) bridge. The physical/bonding interfaces don't have IP addresses. To detect the correct interface in that situation, we should backport the following commits into RHEL8.2 and RHEL8.4. ~~~ commit 40d05029ce0b2ad437377cf9a8bcb4c91508fa89 Author: Heitor R. Alves de Siqueira <halves> Date: Thu Mar 21 16:29:33 2019 -0300 ethmonitor: check if interface exists by link --- commit c0ac191c73f1a3cf62d54b7ec59992997cca3810 Author: Heitor Alves de Siqueira <halves> Date: Wed Apr 17 17:16:39 2019 -0300 ethmonitor: fix is_interface() regression Commit 40d05029ce0b changed is_interface() to list by link instead of address. We need to adjust the grep filter for the new output format, else we'll miss interfaces. --- commit 7f7ca75100a846242ff1510fd9bcf299cd3d00eb Author: Aleksei Burlakov <aleksei.burlakov> Date: Mon Oct 26 13:25:45 2020 +0100 ethmonitor: is_interface: RE matches vlan names Vlan names end not with : but are suffixed with the @devices-name ~~~ Version-Release number of selected component (if applicable): resource-agents in RHEL8.2 and RHEL8.4. How reproducible: Everytime when ethmonitor's monitor operation runs. Steps to Reproduce: 1. Configure an interface which belongs to ovs-bridge. 2. Setup ethmonitor for the bonding device which doesn't have an IP address. 3. Observe the error message is shown. Actual results: The warning message is shown Expected results: The warning message is not shown. Additional info: The message makes user confused. We should prevent it.