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

2021-08-03 Thread Lee Yarwood
** Changed in: nova Status: In Progress => Fix Released -- 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/1919357 Title: "Secure live migration with QEMU-native TLS

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

2021-06-03 Thread Elod Illes
** Changed in: nova/ussuri Status: New => Fix Released ** Changed in: nova/victoria Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

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

2021-06-03 Thread Elod Illes
** Changed in: nova/train Status: New => Fix Released -- 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/1919357 Title: "Secure live migration with QEMU-native TLS

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

2021-03-17 Thread Balazs Gibizer
** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Josephine Seifert (josei) ** Changed in: nova Importance: Undecided => High ** Also affects: nova/stein Importance: Undecided Status: New ** Also affects: nova/victoria

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

2021-03-16 Thread Jeremy Stanley
We discussed this at some length earlier today in the #openstack-nova IRC channel: http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack- nova.2021-03-16.log.html#t2021-03-16T14:31:57 Given that the information is already public, and the bug in this case is incomplete