Project

General

Profile

Bug #43188

Dynamic resharding not working for empty zonegroup in period

Added by Or Friedmann 12 months ago. Updated 9 months ago.

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

0%

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

Description

Sometimes when cluster has been upgraded from jewel, the period's zonegroup could be empty, so no dynamic resharding with message: resharding is disabled


Related issues

Copied to rgw - Backport #43851: nautilus: Dynamic resharding not working for empty zonegroup in period Resolved

History

#1 Updated by Casey Bodley 12 months ago

can you share some steps to reproduce this broken period configuration?

#2 Updated by Casey Bodley 12 months ago

  • Status changed from New to Fix Under Review

#3 Updated by Or Friedmann 11 months ago

Hi Casey,

Way to procedure:
1) Install cluster with Jewel 10.2.2 (with running RGW and at least one bucket and one object)
2) Upgrade to Luminous 12.2.12 (probably will produce even with a lower version)
3) radosgw-admin period list (will return empty list), radosgw-admin realm list (will return empty list)
4) dynamic resharding will not work

I have checked it again, the main problem there is that after upgrading from Jewel to Luminous the realm is empty without any zonegroup inside, the period is empty too.
It means that the check for exactly one zonegroup will fail and will cause dynamic resharding not working.

#4 Updated by Casey Bodley 10 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to nautilus

#5 Updated by Nathan Cutler 10 months ago

  • Copied to Backport #43851: nautilus: Dynamic resharding not working for empty zonegroup in period added

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