Project

General

Profile

Actions
Copy link

Bug #47323

closed

monitoring: Use null yaxes min for OSD read latency

Added by Seena Fallah over 3 years ago. Updated about 3 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 2 (0 open — 2 closed)

Copied to mgr - Backport #47995: nautilus: monitoring: Use null yaxes min for OSD read latencyResolvedLaura PaduanoActions
Copied to mgr - Backport #47996: octopus: monitoring: Use null yaxes min for OSD read latencyResolvedLaura PaduanoActions
Actions
Copy link
 #1

Updated by Neha Ojha over 3 years ago

  • Category set to 148
  • Status changed from New to Fix Under Review
Actions
Copy link
 #2

Updated by Lenz Grimmer over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v16.0.0
Actions
Copy link
 #3

Updated by Nathan Cutler over 3 years ago

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

Updated by Nathan Cutler over 3 years ago

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

Updated by Nathan Cutler over 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".

Actions
Copy link
 #6

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 148 to Monitoring
Actions
Copy link

Also available in: Atom PDF