Improper handling of return code 202 in some cases
Bug #1007447 reported by
David Kranz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
High
|
David Kranz |
Bug Description
There are some race conditions in the code caused by the following type of sequence:
1. Delete a resource
2. Verify 202 is returned
3. Assert that a listing of the resource class does not contain the deleted resource
This is not right because 202 means there is no guarantee that the delete will be acted on immediately. They need to loop for some time waiting for the deletion. We have code that waits for a server to be deleted and this is the same issue. I got a test failure for the one at test_floating_
test_volumes_get:55
Changed in tempest: | |
assignee: | nobody → David Kranz (david-kranz) |
Changed in tempest: | |
status: | Fix Committed → Fix Released |
Changed in tempest: | |
milestone: | none → havana-3 |
To post a comment you must log in.
David, want to give this one a hack?