Tempest failures on NodeLocked/Conflict errors need workaround
Bug #1316773 reported by
Adam Gandelman
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
High
|
David Shrewsbury |
Bug Description
Tempest seems to be periodically failing in the tearDown of tempest.
2014-05-06 15:31:31.117 8282 ERROR wsme.api [-] Server-side error: "Node ad0119dc-
http://
Changed in ironic: | |
importance: | Medium → High |
Changed in ironic: | |
assignee: | nobody → David Shrewsbury (dshrews) |
Changed in ironic: | |
assignee: | David Shrewsbury (dshrews) → nobody |
Changed in ironic: | |
milestone: | none → juno-3 |
Changed in ironic: | |
status: | Fix Committed → Fix Released |
Changed in ironic: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
I can confirm this problem (with exception that error now is Conflict). This is something that should be fixed by https:/ /review. openstack. org/#/c/ 94923/ in the long term and may need a workaround either in Tempest or in client for now (just retrying should be enough).