Masahito Muroi
509820f156
The request_specs_dict in the _list_view is initialized as a defaultdict object in order to return empty string as default. But the request_spec_dict is replaced with a normal dict object in the v2.96 microversion, then if server list and RequestSpec missmatch happens by any reason, the List Server API and the List Server Detail API hit 500 Internal server error because of key error. This commit updates the req_spec_dict to use normal dict object, then it returns sentinel object if there is no appropriate request_spec object. Closes-Bug: #2095364 Change-Id: If282b8709954f276cb5d48114437809d771a9958
16 lines
787 B
YAML
16 lines
787 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #2095364`_: Fixed the List Server API and the List Server Detail API
|
|
500 Internal Server Error issue in v2.96 or later API microversion if
|
|
one or more instance has no request spec object. One usecase was when cloud
|
|
user tried to create instance which exceeded their quota, the request does
|
|
not create instance request spec. Once the no request spec instance is
|
|
created in cloud user project, the server list API and the list server
|
|
details API return 500 Internal Server Error for the project until the
|
|
cloud user deletes the no request spec object instance.
|
|
After this fix, the v2.96 or later returns `null` at the
|
|
`pinned_availability_zone` value if not specified.
|
|
|
|
.. _Bug #2095364: https://launchpad.net/bugs/2095364
|