Change-Id: I538b9b143c868d9419709356daf0ffc48e2f0df9
Closes-Bug: #1932194
(cherry picked from commit 5c6fd44504e47ddbec3e0c29d454daeda87f86a4)
35519c0...
by
Dmitriy Rabotyagov <email address hidden>
Search in nova services instead of hypervisors
Nova services and hypervisor naming can differ, as they retireve node
names in different way.
In the meanwhile we operate with nova.services while enabling/disabling
nodes duringh the incident. So we're supposed to have in database record
matching to what we have in service list, but not in hypervisor list.
Closes-Bug: #1839715
Change-Id: I9c591d33f17a8d5950bdb1fc2d686e2301fc6d95
(cherry picked from commit 4322968b893b242f229912c2b70e3895f0227402)
This patch fixes the code that assignes aggregates to the reserved_host.
The existing code only assigned a aggregate that first matched failed
compute host name.
By this fix, all aggregates that ware assigned to the failed host can
be assigned to the reserved_host.
Closes-Bug: #1856164
Change-Id: I8a727e3c50b71a5ad52d58d0ba3bde4f09446748
(cherry picked from commit d1850df674aa3390413ead9b07faa2ba5d7dbea4)
If you request to show details of versions "v1/" API it returns 404
ResourceNotFound.
This patch fixes this issue by updating the v1 version correctly
as "v1.0" in versions controller which helps wsgi layer to find
the resource(controller) correctly. This way it returns the details
of version "v1" correctly instead of ResourceNotFound.
This patch fixes the reported supported microversion as well
to avoid clients failing due to requesting too new version
(LP#1882516). It has to be fixed to pass tests.
APIImpact - versions "v1/" show API will return 200 OK now instead
of 404 ResourceNotFound.
