Placement duplicate aggregate uuid handling during concurrent aggregate create insufficiently robust
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Jay Pipes |
Bug Description
NOTE: This may be just a postgresql problem, not sure.
When doing some further experiments with load testing placement, my resource provider create script, which uses asyncio was able to cause several 500 errors from the placement service of the following form:
```
cdent-a01:
2018-08-12 16:03:30.698 9 DEBUG nova.api.
2018-08-12 16:03:30.903 9 ERROR nova.api.
2018-08-12 16:03:30.914 9 INFO nova.api.
```
"DETAIL: Key (uuid)=
This is because the code at https:/
It's not clear to me if this is because oslo_db is not transforming the postgresql error properly or that the generic error there is the wrong one and we've never noticed before because we don't hit the concurrency situation hard enough.
Changed in nova: | |
assignee: | Jay Pipes (jaypipes) → Chris Dent (cdent) |
Which version of postgresql are you using? I'm guessing 8.x?
This is the oslo.db code that is meant to translate the IntegrityError:
http:// git.openstack. org/cgit/ openstack/ oslo.db/ tree/oslo_ db/sqlalchemy/ exc_filters. py#n104