[Yahoo-eng-team] [Bug 2060812] [NEW] removing floating ip from server does not check the server

Public bug reported: A floating Ip can be removed from a server with the following CLI command: openstack server remove floating IP The documentation says, it will remove the floating IP from the given server:

[Yahoo-eng-team] [Bug 2060808] Re: already associated floating ip can be associated to another server without check or warning

** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/2060808 Title: already associated floating ip can be

[Yahoo-eng-team] [Bug 2060808] [NEW] already associated floating ip can be associated to another server without check or warning

Public bug reported: When adding a floating ip to a server the following CLI command is used: openstack server add floating ip When nova was still handling the floating IPs in the backend, it seems there was a check, whether the floating IP was already associated to an instance:

[Yahoo-eng-team] [Bug 1919357] [NEW] "Secure live migration with QEMU-native TLS in nova"-guide misses essential config option

*** This bug is a security vulnerability *** Private security bug reported: - [x] This doc is inaccurate in this way: __ I followed the guide to setup qemu native tls for live migration. After checking, that libvirt is able to use tls using tcpdump to listen on the port for tls, I also

[Yahoo-eng-team] [Bug 1793159] [NEW] no signature check for cached images

Public bug reported: Currently Nova only checks an image's signature directly after downloading it from Glance. The image is then cached on the corresponding compute node. When Nova is reading the image file from cache and actually transfers it into the desired target storage when creating a