2386e015ef
oslo.versionedobjects merged a patch [1] resulting in the referenced bug. A second patch [2] was merged that was supposed to fix the issue. If coerce's value arg is a unicode string, then the method will return unicode [3]. Subsequent checks for isinstance(str) [4] will fail and a TypeError will be raised trying to handle the uuid as an int in the else block. This change ensures that the uuid is an instance of str so that it is handled properly. This problem was fixed in pypowervm 1.1.15 [5] and the minimum version was bumped for master. However, we can't backport the pypowervm requirements bump to the stable branches so we have to fix it here. [1] https://review.openstack.org/#/c/559815/ [2] https://review.openstack.org/#/c/561674/ [3] https://review.openstack.org/#/c/561674/2/oslo_versionedobjects/fields.py@367 [4] https://github.com/powervm/pypowervm/blob/1.1.10/pypowervm/utils/uuid.py#L50-L56 [5] https://github.com/powervm/pypowervm/commit/d55b4c84 Change-Id: I1baef962b4b8074f3f9b9ad5402970edc9a3a776 Related-Bug: #1766692 |
||
---|---|---|
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 | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tests-py3.txt | ||
tox.ini |
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: