Project

General

Profile

Fix #44620

mgr/dashboard: Pool form max size

Added by Stephan Müller 5 months ago. Updated about 1 month ago.

Status:
Pending Backport
Priority:
Normal
Category:
dashboard/pools
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus, nautilus
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

Currently the pool form max size is determined by "max_size" of the selected rule or the maximum amount of available OSDs. The amount can be wrong if the failure domain of the rule is not OSD.

I'm also currently not sure if "max_size" and "min_size" are useful values to show, at least pools created on a vstart cluster always show the same min and max size values. Please make that sure that those values can still be used safely.


Related issues

Copied to mgr - Backport #45889: octopus: mgr/dashboard: Pool form max size In Progress
Copied to mgr - Backport #46387: nautilus: mgr/dashboard: Pool form max size New

History

#1 Updated by Stephan Müller 4 months ago

  • Status changed from New to In Progress

#2 Updated by Stephan Müller 3 months ago

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

#3 Updated by Stephan Müller 3 months ago

  • Backport set to octopus

#4 Updated by Lenz Grimmer 2 months ago

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

#5 Updated by Nathan Cutler 2 months ago

  • Copied to Backport #45889: octopus: mgr/dashboard: Pool form max size added

#6 Updated by Stephan Müller about 1 month ago

  • Pull request ID changed from 32829 to 35051

Somehow I copied the wrong PR ID. Change it to the right ID. Sorry for the irritation among the backporters.

#7 Updated by Stephan Müller about 1 month ago

  • Backport changed from octopus to octopus, nautilus

#8 Updated by Nathan Cutler about 1 month ago

  • Copied to Backport #46387: nautilus: mgr/dashboard: Pool form max size added

Also available in: Atom PDF