
Since Icb971831c8d4fe5f940d9e7993d53f1c3765e30f merged in devstack to use the Queens UCA, the nova-multiattach job has been failing to start nova-compute due to permission errors connecting to libvirt, which probably has something to do with the stack user not having access to the proper libvirt(d) group. It's weird since this was working in change I0962474ff6dfc5fa97670c09a1af97a0f34cd54f to make the nova-multiattach job use the Queens UCA. Anyway, let's make it non-voting to stop the bleeding while we can figure out the actual problem. Change-Id: I3911c902cecfa8e66fccffd9fe0e4f462eacd588 Related-Bug: #1763382
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: