Project

General

Profile

Bug #39287

multisite: period pusher gets 403 Forbidden against other zonegroups

Added by Casey Bodley about 1 year ago. Updated 8 months ago.

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

0%

Source:
Tags:
multisite zonegroup
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

RGWPeriodPusher is responsible for sending new period configurations from the master zonegroup to other zonegroups, and from the master zone of each zonegroup to its peer zones. The inter-zone messages are authenticated using the local zone's system_key. However, the inter-zonegroup messages use an empty key, and are rejected with 403 Forbidden. The inter-zonegroup messages should authenticate with the same system_key from the local zone.


Related issues

Copied to rgw - Backport #39413: luminous: multisite: period pusher gets 403 Forbidden against other zonegroups Rejected
Copied to rgw - Backport #39414: nautilus: multisite: period pusher gets 403 Forbidden against other zonegroups Resolved
Copied to rgw - Backport #39415: mimic: multisite: period pusher gets 403 Forbidden against other zonegroups Resolved

History

#1 Updated by Casey Bodley about 1 year ago

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

#2 Updated by Casey Bodley about 1 year ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #39413: luminous: multisite: period pusher gets 403 Forbidden against other zonegroups added

#4 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #39414: nautilus: multisite: period pusher gets 403 Forbidden against other zonegroups added

#5 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #39415: mimic: multisite: period pusher gets 403 Forbidden against other zonegroups added

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