If-None-Match doesn't work on deleted object

[Thomas Herve]

Considering the following scenario

put_object('mycontainer', 'myobj1', 'content', headers={'if-none-match': '*'})
delete_object('mycontainer', 'myobj1')
put_object('mycontainer', 'myobj1', 'content', headers={'if-none-match': '*'})

As of swift master, the last put_object fails with a 412, even if the object has been deleted. It looks like it may be a regression of https://review.openstack.org/281636/

[Christian Schwede (cschwede)]

I can confirm this, and indeed it looks like commit ddeb0cde9fc828fa79dce90df4975f66737ba054 introduced this.

Doesn't work after that commit, but works fine before this. Problem is https://github.com/openstack/swift/blob/master/swift/obj/server.py#L688-L696

[Christian Schwede (cschwede)]

Updated functional test that fails on master, but succeeds on ddeb0cde9fc828fa79dce90df4975f66737ba054~1.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/395582
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=2bdf61fadda655323a36185f921f8a3e183bcdf9
Submitter: Jenkins
Branch: master

commit 2bdf61fadda655323a36185f921f8a3e183bcdf9
Author: Thomas Herve <email address hidden>
Date: Wed Nov 9 14:02:23 2016 +0100

    Handle deleted files with if-none-match

    When an object is deleted, we retrieve its metadata on the next PUT
    requests, which make if-none-match requests fail while the object
    shouldn't be here. It seems we're only interested in the timestamp of
    the deleted object, so get that but forget the metadata.

    Change-Id: I4a4a8be9b631598ca1cd52c53885c68c3fbdfc4a
    Closes-Bug: #1640448

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/swift 2.12.0 release.