Project

General

Profile

Actions
Copy link

Bug #49357

closed

multisite: etag verifier misidentifies multipart uploads with only one part

Added by Casey Bodley about 3 years ago. Updated about 3 years ago.

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

0%

Source:
Tags:
multisite etag
Backport:
pacific octopus nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
39569
Crash signature (v1):
Crash signature (v2):

Description

this causes it to generate a non-multipart etag, so the comparison fails:

ERROR: source and destination objects don't match. Expected etag:59adb24ef3cdbe0297f05b395827453f-1 Computed etag:d41d8cd98f00b204e9800998ecf8427e

Related issues 3 (0 open — 3 closed)

Copied to rgw - Backport #49380: octopus: multisite: etag verifier misidentifies multipart uploads with only one partResolvedNathan CutlerActions
Copied to rgw - Backport #49381: pacific: multisite: etag verifier misidentifies multipart uploads with only one partResolvedsinguliere _Actions
Copied to rgw - Backport #49382: nautilus: multisite: etag verifier misidentifies multipart uploads with only one partResolvedActions
Actions
Copy link
 #2

Updated by Nathan Cutler about 3 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 39569
Actions
Copy link
 #3

Updated by Casey Bodley about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49380: octopus: multisite: etag verifier misidentifies multipart uploads with only one part added
Actions
Copy link
 #5

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49381: pacific: multisite: etag verifier misidentifies multipart uploads with only one part added
Actions
Copy link
 #6

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49382: nautilus: multisite: etag verifier misidentifies multipart uploads with only one part added
Actions
Copy link
 #7

Updated by Loïc Dachary about 3 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
Copy link

Also available in: Atom PDF