Project

General

Profile

Bug #43177

mgr/dashboard: smartctl data shown not integrated in tabset

Added by Patrick Seidensal about 1 year ago. Updated 3 months ago.

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

0%

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

Description

When multiple devices are attached on a host, selecting a host leads to SMART data being shown outside of the tabset. Each device gets its own tabset, instead of all devices being integrated in one tabset.

bug.png View (895 KB) Patrick Seidensal, 12/06/2019 02:39 PM

smart.json (21.5 KB) Kiefer Chang, 12/07/2019 06:00 AM


Related issues

Related to mgr - Feature #42064: mgr/dashboard: add smartctl data as an details tab of a host Resolved
Copied to mgr - Backport #47658: octopus: mgr/dashboard: smartctl data shown not integrated in tabset Resolved

History

#1 Updated by Patrick Seidensal about 1 year ago

  • Related to Feature #42064: mgr/dashboard: add smartctl data as an details tab of a host added

#2 Updated by Kiefer Chang about 1 year ago

Attach the JSON response from backend.

#3 Updated by Kiefer Chang 4 months ago

  • Status changed from New to In Progress
  • Assignee changed from Patrick Seidensal to Kiefer Chang
  • Backport set to octopus
  • Affected Versions v15.2.5, v16.0.0 added
  • Affected Versions deleted (v15.0.0)

After talking with Patrick, I'll work on this issue.

#4 Updated by Kiefer Chang 4 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 37275

#5 Updated by Lenz Grimmer 4 months ago

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

#6 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #47658: octopus: mgr/dashboard: smartctl data shown not integrated in tabset added

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