[tempest integration] patch claim returning 404s

Bug #1328111 reported by Malini Kamalambal on 2014-06-09
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
zaqar
Medium
Unassigned
Juno
Medium
Unassigned

Bug Description

Patch Claim returns 404 when running tempest tests at the gate against devstack
See logs here http://logs.openstack.org/44/94944/10/experimental/check-tempest-dsvm-marconi/23262b7/

NOTE: I haven't been able to repro this when running the tests against my local devstack instance

Changed in marconi:
importance: Undecided → Medium
assignee: nobody → Malini Kamalambal (malini-pk)
Changed in marconi:
milestone: none → graduation
milestone: graduation → juno-2
Kurt Griffiths (kgriffs) wrote :

Looking at these lines:

2014-06-05 21:49:43,181 Request (TestClaims:test_update_claim): 201 POST http://127.0.0.1:8888/v1/queues/Queues-Test-939712936/claims 0.009s

2014-06-05 21:49:43.227 | 2014-06-05 21:49:43,194 Request (TestClaims:test_update_claim): 404 PATCH http://127.0.0.1:8888/v1/queues/Queues-Test-939712936/claims/63c9a59f 0.005s

Seems that these are executing almost simultaneously. Check out the timestamps:

2014-06-05 21:49:43,181
2014-06-05 21:49:43.227

Are these by chance executing in parallel, or does the previous command return before the following is executed?

Malini Kamalambal (malini-pk) wrote :

I had the same thought & so tried adding a sleep of 5 seconds between post claim & update claim in a subsequent patchset.
Tht one still returned a 404 . See logs here http://logs.openstack.org/44/94944/11/experimental/check-tempest-dsvm-marconi/f5ec6a0/console.html.gz

Flavio Percoco (flaper87) wrote :

I'm setting this as Invalid since we've not been able to reproduce it and it's been stalled for quite a bit.

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

Other bug subscribers