Actions
Documentation #41389
closedwrong datatype describing crush_rule
% Done:
0%
Tags:
Backport:
mimic, nautilus, luminous
Reviewed:
Affected Versions:
Pull request ID:
Description
current documentation for luminous https://docs.ceph.com/docs/luminous/rados/operations/pools/ is wrong regarding crush_rule specifying it as integer but it is actually a string.
crush_rule
Description: The rule to use for mapping object placement in the cluster.
Type: Integer
Its wrong in mimic/nautilus docs as well, but it has been corrected on master (so theres a doc change that haven't been backported)
https://docs.ceph.com/docs/master/rados/operations/pools/
Updated by Neha Ojha over 4 years ago
- Assignee set to Deepika Upadhyay
Just needs a cherry-pick of 3ed3de6c964ba998d5b18ceb997d1a6dffe355db
Updated by Deepika Upadhyay over 4 years ago
- Status changed from New to Pending Backport
Updated by Deepika Upadhyay over 4 years ago
- Backport changed from mimic,nautilus to mimic, nautilus
Updated by Deepika Upadhyay over 4 years ago
- Backport changed from mimic, nautilus to nautilus
Updated by Deepika Upadhyay over 4 years ago
- Backport changed from nautilus to mimic, nautilus
Updated by Deepika Upadhyay over 4 years ago
- Copied to Backport #43315: mimic:wrong datatype describing crush_rule added
Updated by Deepika Upadhyay over 4 years ago
- Copied to Backport #43316: nautilus:wrong datatype describing crush_rule added
Updated by Deepika Upadhyay over 4 years ago
- Status changed from Pending Backport to In Progress
Updated by Nathan Cutler over 4 years ago
- Status changed from In Progress to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Backport changed from mimic, nautilus to mimic, nautilus, luminous
Updated by Deepika Upadhyay over 4 years ago
- Copied to Backport #43325: luminous: wrong datatype describing crush_rule added
Updated by Nathan Cutler over 4 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