DLO Delete of object

Bug #1682116 reported by Archana on 2017-04-12
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Wishlist
Christopher Bartz

Bug Description

# swift list archu12320DLO
jcloudsd787f
jcloudsd787f/dlo/00000000
jcloudsd787f/dlo/00000001

[root@jupiter-vm910 ~]# curl -v -X DELETE -H 'X-Auth-Token: 4ed4343037ea46198bde72a911bc8350' http://x.xx.xx.xx:8091/v1/AUTH_f9d7c1cf6500469b80f0906f5f9b1791/archu12320DLO/jcloudsd787f
* About to connect() to x.xx.xx.xx port 8091 (#0)
* Trying 9.47.82.164...
* Connected to x.xx.x.xxx (x.xx.xx.xx) port 8091 (#0)
> DELETE /v1/AUTH_f9d7c1cf6500469b80f0906f5f9b1791/archu12320SLO/jcloudsd787f HTTP/1.1
> User-Agent: curl/7.29.0
> Host: x.xx.xx.xx:8091
> Accept: */*
> X-Auth-Token: 4ed4343037ea46198bde72a911bc8350
>
< HTTP/1.1 204 No Content
< Content-Length: 0
< Content-Type: text/html; charset=UTF-8
< X-Trans-Id: txcfe3fc83e76d40f99649a-0058ee20ba
< Date: Wed, 12 Apr 2017 12:42:34 GMT
<
* Connection #0 to host x.xx.xx.xx left intact

[root@jupiter-vm910 ~]# swift list archu12320SLO
jcloudsd787f/dlo/00000000
jcloudsd787f/dlo/00000001

Deleting of DLO object using CURL does not delete the segments. It does deletion of Manifest file alone. Is there any header required for DLO object deletion.

Janie Richling (jrichli) wrote :

You must use the query parameter ?multipart-manifest=delete as described in : https://docs.openstack.org/developer/swift/overview_large_objects.html#deleting-a-large-object

Tim Burke (1-tim-z) wrote :

Only works for SLO, not DLO:

$ curl -v http://saio:8090/v1/AUTH_test/c/dlo
* Hostname was NOT found in DNS cache
* Trying 127.0.0.1...
* Connected to saio (127.0.0.1) port 8090 (#0)
> GET /v1/AUTH_test/c/dlo HTTP/1.1
> User-Agent: curl/7.35.0
> Host: saio:8090
> Accept: */*
>
< HTTP/1.1 200 OK
< Etag: "b5475dd0366e267565cd45fd086d73dd"
< Content-Length: 8
< Accept-Ranges: bytes
< Last-Modified: Wed, 27 Sep 2017 19:46:13 GMT
< X-Object-Manifest: c/s
< X-Timestamp: 1506541572.66944
< Content-Type: application/x-www-form-urlencoded
< X-Trans-Id: txf36f537bc3fa45c597230-0059cc002b
< X-Openstack-Request-Id: txf36f537bc3fa45c597230-0059cc002b
< Date: Wed, 27 Sep 2017 19:46:51 GMT
<
* Connection #0 to host saio left intact
12345678

$ curl -v http://saio:8090/v1/AUTH_test/c/dlo?multipart-manifest=delete -X DELETE
* Hostname was NOT found in DNS cache
* Trying 127.0.0.1...
* Connected to saio (127.0.0.1) port 8090 (#0)
> DELETE /v1/AUTH_test/c/dlo?multipart-manifest=delete HTTP/1.1
> User-Agent: curl/7.35.0
> Host: saio:8090
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/plain
< X-Trans-Id: tx74299dce56464280ba2c6-0059cc0042
< X-Openstack-Request-Id: tx74299dce56464280ba2c6-0059cc0042
< Date: Wed, 27 Sep 2017 19:47:14 GMT
< Transfer-Encoding: chunked
<
Number Deleted: 0
Number Not Found: 0
Response Body:
Response Status: 400 Bad Request
Errors:
* Connection #0 to host saio left intact
/c/dlo, Not an SLO manifest

Seems like a legit feature request to me.

Changed in swift:
status: New → Confirmed
importance: Undecided → Wishlist
Changed in swift:
assignee: nobody → Christopher Bartz (bartz)

Fix proposed to branch: master
Review: https://review.openstack.org/527744

Changed in swift:
status: Confirmed → In Progress

+1, Any expectations when this fix also will be merged to master, there is no activity during one year ((

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers