7cad745eba
Nova support tagging of instance or other resource like device etc. But those tags are allowed to be as empty string which does not make much sense or any real use case. Updating single tag with empty string is not possible as it will be 404 due to url itself has single tag as id. But updating all tags with few or all of them as empty string does not complain. In those cases, empty tags are being accepted and stored as same. Main issue with those is that empty tag cannot be deleted/show as single tag as it will again 404 with url not found. Only way to delete/show such tag is to delete all together. Empty tag should not be allowed at first. This commit makes empty string request to 400 which are currently 200. Doing for server and device tags and same can be adopted for other resource tagging also if any in future. Fixing this as bug fix hoping no backward incompatibility logically. If such tag could have been deleted alone then we could have fix this with microversion. Change-Id: I18a81f19205b2a40ca470067a9576f2f72ff0f13 Closes-Bug: #1648663
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:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://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:
http://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: