3936a3cfda
When we destroy a flavor it's happening in the API database now. Right after we delete the flavor, we send a delete notification which will attempt to lazy-load projects, but because the flavor is deleted, that will result in a FlavorNotFound from the API DB in method _get_projects_from_db. Because of our fallback code to the main cell DB we'll then call flavor_access_get_by_flavor_id which returns an empty list and that's what goes into the notification, but it's not accurate since the empty list implies there are/were no projects with access to that flavor, when in reality we don't know. This handles the delete notification case by orphaning the flavor object so that when the notification emit happens, the NotificationPayloadBase gets an OrphanedObjectError and just sets projects to None, which is a better representation in the notification payload that we don't have that data. The tests needed some work since they were not actually comparing the payload to the flavor object before, they were comparing to fields in the DB representation of the flavor, which doesn't include the projects field as it's a joined column. Change-Id: I6868efab22cf9f1eb9006589a5b62618434c3ba3 Closes-Bug: #1687012
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 and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
https://docs.openstack.org/developer/nova/feature_classification.html
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: