one extra_specs key still exist when delete one flavor's two extra_specs keys at same time
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
1、posts two requests at same time to delete same flavor's two extra_specs keys
2、the two requests all get success from nova
3、finds only one extra_specs keys be deleted
that seems when handles the first delete request, the delete function of /nova/api/
see [1][2][3][4]:
[1]https:/
[2] https:/
[3] https:/
[4] https:/
| summary: |
- one extra spec key still exist when delete one flavor two extra_specs - keys at same time + one extra_specs key still exist when delete one flavor's two + extra_specs keys at same time |
| description: | updated |
| description: | updated |
| tags: | added: race-condition |
| Matt Riedemann (mriedem) wrote | #1 |
| Changed in nova: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Matt Riedemann (mriedem) wrote | #2 |
| David Li (ldone) wrote | #3 |
Yeah without etags or generations this is kind of hard to enforce from a concurrency perspective in the API. There is a similar bug for updating server metadata concurrently.