Feature #42979
mgr/dashboard: add popover list of Stand-by Managers & Metadata Servers (MDS) in landing page
Status:
Resolved
Priority:
Normal
Assignee:
Category:
dashboard/landingpage
Target version:
% Done:
0%
Source:
Q/A
Tags:
Backport:
octopus, nautilus
Description
Sensible suggestion from QE team:
"On the Landing page, placing the pointer on the standby daemons of Manager servers should list the daemons respectively.
The behavior should be similar to currently available ; Manager - active daemon."
This could easily be extended to MDS (Metadata Servers) as well.
Related issues
History
#1 Updated by Ernesto Puerta 11 months ago
- Subject changed from mgr/dashboard: add popover list of managers in landing page to mgr/dashboard: add popover list of Metadata Servers (MDS) in landing page
#2 Updated by Ernesto Puerta 11 months ago
- Subject changed from mgr/dashboard: add popover list of Metadata Servers (MDS) in landing page to mgr/dashboard: add popover list of Stand-by Managers & Metadata Servers (MDS) in landing page
#3 Updated by Ernesto Puerta 11 months ago
- Description updated (diff)
#4 Updated by Ernesto Puerta 11 months ago
- Pull request ID set to 33529
#5 Updated by Ernesto Puerta 11 months ago
- Status changed from New to In Progress
- Assignee set to avan thakkar
- Backport set to nautilus
#6 Updated by Lenz Grimmer 10 months ago
- Status changed from In Progress to Pending Backport
- Target version changed from v15.0.0 to v16.0.0
- Backport changed from nautilus to octopus, nautilus
Fix was merged into master via PR#33529, needs to be backported into octopus and nautilus.
#7 Updated by Ernesto Puerta 10 months ago
- Copied to Backport #44696: nautilus: mgr/dashboard: add popover list of Stand-by Managers & Metadata Servers (MDS) in landing page added
#8 Updated by Ernesto Puerta 10 months ago
- Copied to Backport #44697: octopus: mgr/dashboard: add popover list of Stand-by Managers & Metadata Servers (MDS) in landing page added
#9 Updated by Nathan Cutler 6 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".