We are glad to announce the release of: nova 23.2.0: Cloud computing fabric controller This release is part of the wallaby stable release series. The source is available from: https://opendev.org/openstack/nova Download the package from: https://tarballs.openstack.org/nova/ Please report issues through: https://bugs.launchpad.net/nova/+bugs For more details, please see below. 23.2.0 ^^^^^^ Known Issues ************ * The libvirt virt driver in Nova implements power on and hard reboot by destroying the domain first and unpluging the vifs then recreating the domain and replugging the vifs. However nova does not wait for the network-vif-plugged event before unpause the domain. This can cause the domain to start running and requesting IP via DHCP before the networking backend has finished plugging the vifs. The config option [workarounds]wait_for_vif_plugged_event_during_hard_reboot has been added, defaulting to an empty list, that can be used to ensure that the libvirt driver waits for the network-vif-plugged event for vifs with specific "vnic_type" before it unpauses the domain during hard reboot. This should only be used if the deployment uses a networking backend that sends such event for the given "vif_type" at vif plug time. The ml2/ovs and the networking-odl Neutron backend is known to send plug time events for ports with "normal" "vnic_type". For more information see https://bugs.launchpad.net/nova/+bug/1946729 * Linux guest images that have known kernel bugs related to virtualized apic initialization previously would sporadically hang. For images where the kernel cannot be upgraded, a "[workarounds]" config option has been introduced: "[workarounds]libvirt_disable_apic" This option is primarily intended for CI and development clouds as a bridge for operators to mitigate the issue while they work with their upstream image vendors. Bug Fixes ********* * The bug 1952941 is fixed where a pre-Victoria server with pinned CPUs cannot be migrated or evacuated after the cloud is upgraded to Victoria or newer as the scheduling fails with "NotImplementedError: Cannot load 'pcpuset'" error. (https://bugs.launchpad.net/nova/+bug/1952941) Changes in nova 23.1.0..23.2.0 ------------------------------ 5b7cb876ba skip test_tagged_attachment in nova-next 80572cef67 workarounds: Add libvirt_disable_apic dad566614c Migrate RequestSpec.numa_topology to use pcpuset b190c30f00 Reproduce bug 1952941 5f2f283a75 [rt] Apply migration context for incoming migrations 94f17be190 Extend the reproducer for 1953359 and 1952915 d8859e4f95 Reproduce bug 1953359 6c3d5de659 Ensure MAC addresses characters are in the same case 89c4ff5f7b Add a WA flag waiting for vif-plugged event during reboot f950cedf17 Clear rebalanced compute nodes from resource tracker c260e75d01 Add functional regression test for bug 1853009 c8b04d183f Store old_flavor already on source host during resize 140ae45d98 Reproduce bug 1944759 0cd4ef2dcd Parse alias from domain hostdev 2bee83b8a9 compute: Avoid duplicate BDMs during reserve_block_device_name 7a9e3dcd17 Add functional test for bug 1937375 Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 8 +- nova/compute/manager.py | 20 ++ nova/compute/resource_tracker.py | 52 +++++- nova/conf/workarounds.py | 69 +++++++ nova/objects/instance_numa.py | 33 ++-- nova/objects/request_spec.py | 12 ++ .../functional/regressions/test_bug_1853009.py | 200 ++++++++++++++++++++ .../functional/regressions/test_bug_1937375.py | 98 ++++++++++ nova/virt/libvirt/config.py | 4 + nova/virt/libvirt/driver.py | 28 ++- nova/virt/libvirt/migration.py | 11 +- ...-event-during-hard-reboot-fb491f6a68370bab.yaml | 18 ++ ...c-numa-topology-migration-c97dbd51b3c6c116.yaml | 9 + .../libvirt-disable-apic-39599bdc2d110a1f.yaml | 13 ++ 23 files changed, 998 insertions(+), 35 deletions(-)