[Bug 1868364] Re: rgw: unable to abort multipart upload after the bucket got resharded

[Corey Bryant]

Hi dongdong,

Thank you for this. Can you update the [Regression Potential] section to
adhere to the description at
https://wiki.ubuntu.com/StableReleaseUpdates? The regression potential
of an SRU is expected to be low. This section should mention what could
happen if the code were to cause a regression.

Also it seems like the patch has several releases in it. Is that
expected?

Thank you,
Corey

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1868364

Title:
  rgw: unable to abort multipart upload after the bucket got resharded

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive queens series:
  New
Status in Ubuntu Cloud Archive rocky series:
  Won't Fix
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceph package in Ubuntu:
  Fix Released
Status in ceph source package in Bionic:
  Triaged

Bug description:
  [Impact]
  This bug will cause the bucket not able to abort the multipart upload and leaving the stale multiple entries behind for those buckets which had partial multipart uploads before the resharding.

  [Test Case]
  Deploy a latest luminous(12.2.13) ceph cluter
  Create a bucket
  upload a big file (200M+) to that bucket
  Press "Ctrl + C" after several part (each part is 15M) had been uploaded
  Manually reshard the bucket to 4 shards
  Abort the multipart uploading
  Without the fix, you will not able to abort the previous uploading

  [Regression Potential]
  Low - this fix has been accept upstream in later releases since from Mimic.

  [Original Bug Report]
  There is a bug during the resharding for those multipart entries.
  For all the multipart entries, the hash source should be the object name so that all those entries can still be
  distributed to one same bucket index shard object.
  Right now the code just calculate the shard id based on each entry's name, which is wrong
  This can cause the bucket not able to abort the multipart upload and leave the stale multiple entries behind.
  https://tracker.ceph.com/issues/43583

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1868364/+subscriptions