MPU cross-policy-segments writes manifest to wrong policy

Bug #2038459 reported by clayg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
In Progress
Undecided
Alistair Coles

Bug Description

If you carefully construct your +segments container for s3api such that MPU's segments go into a different (e.g. EC) policy than you source bucket (e.g. 3-replica manifests) then when you complete the multi-part-upload with the S3 API call the manifest will get written into the correct bucket - but the wrong policy.

https://review.opendev.org/c/openstack/swift/+/866508

The reconciler will try to fix the SLO-manifest policy but there's another issue there lp bug #2038458 - so better if we just don't do it in the first place.

Changed in swift:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to swift (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/swift/+/897864

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on swift (master)

Change abandoned by "Clay Gerrard <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/swift/+/866508
Reason: we're going to head over this way: https://review.opendev.org/c/openstack/swift/+/897864

Revision history for this message
Alistair Coles (alistair-coles) wrote :

The bug was introduced by introduced by https://review.opendev.org/c/openstack/swift/+/755587)

Changed in swift:
assignee: nobody → Alistair Coles (alistair-coles)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.