Project

General

Profile

Bug #46683

mgr/dashboard: cpu stats incorrectly displayed

Added by Avan Thakkar 6 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
dashboard/monitoring
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

The hosts screen on the dashboard displays incorrect data on the CPU usage for the nodes in the cluster.

Actual results:
The usage is near 0% when in fact the 4 nodes are around 85% busy.

Expected results:
near real-time metrics

cpuscreen.JPG View (55.6 KB) Avan Thakkar, 07/23/2020 06:06 AM


Related issues

Copied to mgr - Backport #46736: octopus: mgr/dashboard: cpu stats incorrectly displayed Resolved
Copied to mgr - Backport #47573: nautilus: mgr/dashboard: cpu stats incorrectly displayed Resolved

History

#1 Updated by Avan Thakkar 6 months ago

  • Assignee set to Avan Thakkar
  • Pull request ID set to 36258

#2 Updated by Avan Thakkar 6 months ago

  • Backport set to octopus

#3 Updated by Alfonso Martínez 6 months ago

  • Status changed from New to Fix Under Review

#4 Updated by Volker Theile 6 months ago

  • Status changed from Fix Under Review to Pending Backport

#5 Updated by Lenz Grimmer 6 months ago

  • Target version set to v16.0.0

#6 Updated by Avan Thakkar 6 months ago

  • Copied to Backport #46736: octopus: mgr/dashboard: cpu stats incorrectly displayed added

#7 Updated by Lenz Grimmer 6 months ago

  • Status changed from Pending Backport to Resolved

#8 Updated by Avan Thakkar 4 months ago

  • Status changed from Resolved to Pending Backport
  • Backport changed from octopus to octopus, nautilus

#9 Updated by Avan Thakkar 4 months ago

  • Copied to Backport #47573: nautilus: mgr/dashboard: cpu stats incorrectly displayed added

#10 Updated by Lenz Grimmer 4 months ago

  • Category set to dashboard/monitoring

#11 Updated by Nathan Cutler 4 months 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".

Also available in: Atom PDF