Project

General

Profile

Bug #47323

monitoring: Use null yaxes min for OSD read latency

Added by Seena Fallah 5 months ago. Updated 14 days ago.

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

0%

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

Description

According to seriesOverrides that negative-Y for read param there shouldn't be a minimum for yaxes


Related issues

Copied to mgr - Backport #47995: nautilus: monitoring: Use null yaxes min for OSD read latency Resolved
Copied to mgr - Backport #47996: octopus: monitoring: Use null yaxes min for OSD read latency Resolved

History

#1 Updated by Neha Ojha 4 months ago

  • Category set to dashboard/monitoring
  • Status changed from New to Fix Under Review

#2 Updated by Lenz Grimmer 3 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v16.0.0

#3 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #47995: nautilus: monitoring: Use null yaxes min for OSD read latency added

#4 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #47996: octopus: monitoring: Use null yaxes min for OSD read latency added

#5 Updated by Nathan Cutler 14 days 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