Matt Riedemann 3c1943f8d9 Check for 204 case in DynamicVendorData ... Before b9587587c2 we were doing an explicit check on the response status codes, but after that change, we just rely on the bool override in requests.Reponse which is True for any repsonse code less than 400. In the 204 case we won't have response text, so we should handle that before trying to load the json repsonse text. Because TypeError and ValueError are handled it would just result in a warning if you got a 204, unless CONF.api.vendordata_dynamic_failure_fatal was True in which case it's a failure (as shown in the unit test update here). Change-Id: Iba95fd0112ae4510ef21fdb44fcb281b14567c07 Closes-Bug: #1669084		2017-03-01 14:16:29 -05:00
..
functional	Merge "[placement] Add Traits related table to the api database"	2017-03-01 02:16:24 +00:00
live_migration/hooks	Fix for live-migration job	2016-12-01 09:54:00 +00:00
unit	Check for 204 case in DynamicVendorData	2017-03-01 14:16:29 -05:00
__init__.py	…
fixtures.py	Make servers API use cell-targeted context	2017-02-22 10:33:51 -08:00
uuidsentinel.py	Remove redundant str typecasting	2016-09-23 12:53:34 +05:30