Project

General

Profile

Actions

Bug #52028

closed

mgr/dashboard: Incorrect MTU mismatch warning

Added by Kevin Meijer almost 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Category:
Monitoring
Target version:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
pacific,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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

Screenshot 2021-08-03 at 17.14.32.png (209 KB) Screenshot 2021-08-03 at 17.14.32.png The alert Kevin Meijer, 08/03/2021 03:15 PM

Related issues 2 (0 open2 closed)

Copied to Dashboard - Backport #52616: octopus: mgr/dashboard: Incorrect MTU mismatch warningResolvedAvan ThakkarActions
Copied to Dashboard - Backport #52617: pacific: mgr/dashboard: Incorrect MTU mismatch warningResolvedAvan ThakkarActions
Actions #1

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.

Actions #2

Updated by Ernesto Puerta over 2 years ago

  • Project changed from mgr to Dashboard
  • Category changed from prometheus module to Monitoring
Actions #3

Updated by Ernesto Puerta over 2 years ago

  • Assignee set to Aashish Sharma
Actions #4

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
Actions #5

Updated by Aashish Sharma over 2 years ago

  • Status changed from Triaged to Fix Under Review
  • Pull request ID set to 43019
Actions #6

Updated by Ernesto Puerta over 2 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #7

Updated by Backport Bot over 2 years ago

  • Copied to Backport #52616: octopus: mgr/dashboard: Incorrect MTU mismatch warning added
Actions #8

Updated by Backport Bot over 2 years ago

  • Copied to Backport #52617: pacific: mgr/dashboard: Incorrect MTU mismatch warning added
Actions #9

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".

Actions #10

Updated by Patrick Seidensal about 2 years ago

  • Backport changed from pacific,octopus to pacific,octopus,nautilus
Actions #11

Updated by Patrick Seidensal about 2 years ago

  • Backport changed from pacific,octopus,nautilus to pacific,octopus
Actions

Also available in: Atom PDF