Project

General

Profile

Bug #43097

mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked

Added by Alfonso Martínez 10 months ago. Updated 8 months ago.

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

0%

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

Description

Steps to Reproduce:
1. Navigate to OSDs -> Overall Performance -> R/W Profile
2. The right top of the graph always displays 'Last 36 Hours' irrespective of the time picked.

Expected results:
Should change matching the time picked.


Related issues

Copied to mgr - Backport #43115: mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked Resolved

History

#1 Updated by Alfonso Martínez 10 months ago

  • Status changed from In Progress to Fix Under Review

#2 Updated by Lenz Grimmer 10 months ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Lenz Grimmer 10 months ago

  • Pull request ID set to 31964

#4 Updated by Alfonso Martínez 10 months ago

  • Copied to Backport #43115: mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked added

#5 Updated by Alfonso Martínez 10 months ago

  • Copied to deleted (Backport #43115: mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked)

#6 Updated by Alfonso Martínez 10 months ago

  • Related to Backport #43115: mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked added

#7 Updated by Alfonso Martínez 10 months ago

  • Related to deleted (Backport #43115: mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked)

#8 Updated by Alfonso Martínez 10 months ago

  • Copied to Backport #43115: mgr/dashboard: OSDs: R/W profile displays 'Last 36 hours' always irrespective of the time picked added

#9 Updated by Nathan Cutler 8 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