Deleting volumes produce HTTP 202 error

asked 2013-04-03 01:43:39 -0500

terry-gong gravatar image

In detaching many volumes that I had created, the nova-api log file shows the following error:

2013-04-01 18:30:38.151 INFO nova.osapi_compute.wsgi.server [req-edfa5757-df6f-40a0-a62a-2c8f1191ae2 d 651b1ea1ccc9440082c4284ec36759fb f688d8f77def45bab28eb06f402468af] "DELETE /v2/f688d8 f77def45bab28eb06f402468af/servers/9e5986c9-9855-4e2f-9da5-5d6d85fd2da9/os-volume_attachments/7769a6 56-c640-44ab-8f08-f9399f34fadd HTTP/1.1" status: 202 len: 121 time: 1.0824511

I am using a python program to make direct API calls to the nova client to delete_server_volume. I believed the 202 error mean that the request has been submitted for processing. What is the best practice in handling this type of error to make sure the detach actually happen?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-04-04 01:36:56 -0500

lauria gravatar image


The API in this case is returning a 202 not to indicate an error, but working as designed.

202 is the response code to indicate that an asynchronous operation has ended successfully. This, for the most part, is the response code that is returned by the nova API when a client's request was accepted, but not yet processed.

As far as a built-in mechanism for checking that the operation completed (w/ or w/o errors), I believe that the API does not have an interface for checking the progress of asynchronous operations. This means you would have to poll yourself to get the status of the operation.

edit flag offensive delete link more

answered 2013-04-04 19:05:19 -0500

terry-gong gravatar image

Thanks Giampaolo Lauria, that solved my question.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-04-03 01:43:39 -0500

Seen: 500 times

Last updated: Apr 04 '13