Project

General

Profile

Actions
Copy link

Bug #49791

closed

Fail to download large object when put it with swift api.

Added by zhiming zhang about 3 years ago. Updated almost 3 years ago.

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

0%

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

Description

ceph-14.2.8 version.
Upload a dynamic large object (>5GB) using the Swift interface, if the manifest file and segment are not in the same container and the placement rule of the two containers is different, the upload succeeds but the download fails. When uploading a static large object in this scenario, the upload fails.

First, add two storage class 'A' and 'B' under 'default-placement' in zonegroup and zone, take effect;
Second, modify user default placement to 'default-placement' and default storage class to 'A', create bucket 'bucket-1';
Then, modify user default storage class to 'B', create bucket 'bucket-2';

Upload segments to bucket-1, and manifest file to bucket-2, upload succeeds, bucket download fails, can not find the object.

Related issues 1 (0 open — 1 closed)

Copied to rgw - Backport #50836: nautilus: Fail to download large object when put it with swift api.ResolvedActions
Actions
Copy link
 #1

Updated by Kefu Chai about 3 years ago

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

Updated by Casey Bodley about 3 years ago

  • Backport set to nautilus

does not affect master/pacific. needs a fix on octopus and backport to nautilus

Actions
Copy link
 #4

Updated by Nathan Cutler almost 3 years ago

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

Updated by Backport Bot almost 3 years ago

  • Copied to Backport #50836: nautilus: Fail to download large object when put it with swift api. added
Actions
Copy link
 #6

Updated by Nathan Cutler almost 3 years ago

  • Pull request ID changed from 40106 to 40296
Actions
Copy link
 #7

Updated by Loïc Dachary almost 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