Project

General

Profile

Bug #47323

monitoring: Use null yaxes min for OSD read latency

Added by Seena Fallah about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Monitoring
Target version:
Ceph - v16.0.0
% Done:

0%

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

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 about 3 years ago

  • Category set to 148
  • Status changed from New to Fix Under Review

#2 Updated by Lenz Grimmer about 3 years ago

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

#3 Updated by Nathan Cutler about 3 years ago

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

#4 Updated by Nathan Cutler about 3 years ago

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

#5 Updated by Nathan Cutler almost 3 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".

#6 Updated by Ernesto Puerta over 2 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 148 to Monitoring

Also available in: Atom PDF