Chris Dent c5cdef24ed [placement] add error.code on a ConcurrentUpdateDetected ... A pending api-sig guideline I473918ce9c6b49c0b904e93b7140421525f4e7c0 reflects discussion amongst various parties that adding error codes to structured error responses should not be considered a breaking API change. Given that, it is simply "okay" to add them. This change adds errors.CONCURRENT_UPDATE wherever the ConcurrentUpdateDetected results in an HTTPConflict (409) response. In practice this means that if microversion 1.23 or beyond is being used, there will be a code in any error response, and for some 409 responses that code will be `placement.concurrent_update`. Note that because we haven't instrumented a way to cause a truly concurrent update, we've never had real tests for this kind of thing. Change-Id: I5a164a0ee298846231113ad7b62b82a3e8f1f409		2018-07-11 14:00:57 +01:00
..
ec2	delete more i18n log markers	2017-03-21 07:37:21 -04:00
metadata	metadata: add vf_trusted field to device metadata	2018-05-31 13:55:10 -04:00
openstack	[placement] add error.code on a ConcurrentUpdateDetected	2018-07-11 14:00:57 +01:00
validation	Use nova.db.api directly	2018-07-10 14:56:27 +00:00
__init__.py	Remove unused copyright from nova.api.__init__	2014-01-10 16:24:50 +08:00
auth.py	Refactor WSGI apps and utils to limit imports	2018-03-06 22:05:12 +00:00
compute_req_id.py	Migrate to oslo request_id middleware - mv 2.46	2017-05-27 10:11:44 +00:00
manager.py	Only setup iptables for metadata if using nova-net	2017-07-20 00:00:22 +00:00
wsgi.py	Refactor WSGI apps and utils to limit imports	2018-03-06 22:05:12 +00:00