Change Ic02206e887e3fea7752d615bbed680510c482097 attempted to optimize the GET /servers flow by skipping filtering on build requests if the ip or ip6 filters were used, since servers that are not yet scheduled (build requests) can't have ips. However, if a marker is provided and the marker is in the build_requests table, we fail to look there and then check the cells for the marker, which won't exist and result in a 400 MarkerNotFound error. This fixes the issue by *not* skipping build requests if there is a marker specified. A functional test is added which will show the 400 MarkerNotFound error if the code fix is removed. Change-Id: Ibdd157d06252c3c0219539ec798c8d9d3a8ae26f Closes-Bug: #1777458
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: