Bug #52028
closedmgr/dashboard: Incorrect MTU mismatch warning
0%
Description
Incorrect MTU mismatch warning¶
We're currently getting a lot of MTU mismatch warnings in 16.2.5 indicating a mismatch in MTU on our OSD nodes.
In our case this is actually correct, we have 4 NICs per OSD server, 2 of which are bonded with LACP as our cluster network (MTU 9000) and 2 of which are our public network (MTU 1500).
We also noticed that even though this alert has been muted, we're still getting popups every few seconds.
Environment¶
ceph version
string: ceph version 16.2.5 (0883bdea7337b95e4b611c768c0279868462204a) pacific (stable)- Platform (OS/distro/release): Debian (Running ceph containerized)
- Cluster details (nodes, monitors, OSDs): 3 mons, 4 OSDs
- Browser used (e.g.:
Version 86.0.4240.198 (Official Build) (64-bit)
): Firefox 90.0.2 64-bit
How reproducible¶
Have a host have mixed a MTU setup.
Actual results¶
See attached screenshot
Expected results¶
Nothing
Files
Updated by Kai Stian Olstad over 2 years ago
This issue has also come up in the mailing list where Ernesto asked for more information
https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/message/M2N3BAR5A2S3W4PJMQHOI7NXXT2X4JSC/
Ernesto Puerta wrote: Could you please go to the Prometheus UI and share the output of the following query "node_network_mtu_bytes"? That'd be useful to understand the issue
You also get this warning on NICs that is in DOWN state.
I don't have access to the cluster at the moment so can't add the information Ernesto asks for.
Updated by Ernesto Puerta over 2 years ago
- Project changed from mgr to Dashboard
- Category changed from prometheus module to Monitoring
Updated by Ernesto Puerta over 2 years ago
- Status changed from New to Triaged
- Target version set to v15.2.15
- Source set to Community (user)
- Backport set to pacific,octopus
Updated by Aashish Sharma over 2 years ago
- Status changed from Triaged to Fix Under Review
- Pull request ID set to 43019
Updated by Ernesto Puerta over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #52616: octopus: mgr/dashboard: Incorrect MTU mismatch warning added
Updated by Backport Bot over 2 years ago
- Copied to Backport #52617: pacific: mgr/dashboard: Incorrect MTU mismatch warning added
Updated by Loïc Dachary over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Patrick Seidensal about 2 years ago
- Backport changed from pacific,octopus to pacific,octopus,nautilus
Updated by Patrick Seidensal about 2 years ago
- Backport changed from pacific,octopus,nautilus to pacific,octopus