Project

General

Profile

Bug #37615

The expected output of the "radosgw-admin reshard status" command is not documented

Added by Mark Kogan over 2 years ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
reshard
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Currently, there is no documentation of the expected output from the "radosgw-admin reshard status" command
for determining whether a dynamic resharding has occurred.


Related issues

Copied to rgw - Backport #40355: nautilus: The expected output of the "radosgw-admin reshard status" command is not documented Resolved
Copied to rgw - Backport #40356: luminous: The expected output of the "radosgw-admin reshard status" command is not documented Rejected
Copied to rgw - Backport #40357: mimic: The expected output of the "radosgw-admin reshard status" command is not documented Resolved

History

#2 Updated by Casey Bodley almost 2 years ago

  • Status changed from New to Pending Backport
  • Tags set to reshard
  • Backport set to luminous mimic nautilus

#3 Updated by Nathan Cutler almost 2 years ago

  • Copied to Backport #40355: nautilus: The expected output of the "radosgw-admin reshard status" command is not documented added

#4 Updated by Nathan Cutler almost 2 years ago

  • Copied to Backport #40356: luminous: The expected output of the "radosgw-admin reshard status" command is not documented added

#5 Updated by Nathan Cutler almost 2 years ago

  • Copied to Backport #40357: mimic: The expected output of the "radosgw-admin reshard status" command is not documented added

#6 Updated by Nathan Cutler over 1 year ago

  • Pull request ID set to 25496

#7 Updated by Nathan Cutler over 1 year ago

  • Tracker changed from Documentation to Bug
  • Regression set to No
  • Severity set to 3 - minor

#8 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