6482165bb1
Change I4e755b9c66ec8bc3af0393e81cffd91c56064717 made the [glance]/api_servers option optional. If not set, we attempt to get the image service endpoint via keystoneauth adapter and the service catalog via the request context. Periodic tasks run without an actual token so there is no way to get the service catalog and the KSA adapter code to get the endpoint raises EndpointNotFound when trying to build the "image_ref_url" entry in the legacy instance notification payload. This change simply handles the EndpointNotFound and sets the image_ref_url to the instance.image_ref, which for non-volume-backed instances is the image id (for volume-backed instances it's an empty string). This doesn't affect versioned notifications since those don't use the "image_ref_url" entry in the payload that is created, they just have an "image_uuid" entry in the versioned notification payload which is populated via instance.image_ref. An upgrade impact release note is added in the case that some consuming service is actually relying on that legacy notification field being a URL and parsing it as such. The thinking here, however, is this is better than not sending the field at all, or setting it to None. Long-term this code all gets replaced with versioned notifications. Change-Id: Ie23a9c922776b028da0720c939846cba233ac472 Closes-Bug: #1753550 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
README.rst
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: