March 2022 - Release-announce - lists.openstack.org

ironic-python-agent 6.1.3 (ussuri)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

We are psyched to announce the release of: ironic-python-agent 6.1.3: Ironic Python Agent Ramdisk This release is part of the ussuri stable release series. The source is available from: https://opendev.org/openstack/ironic-python-agent Download the package from: https://tarballs.openstack.org/ironic-python-agent/ Please report issues through: https://storyboard.openstack.org/#!/project/openstack/ironic- python-agent For more details, please see below. 6.1.3 ^^^^^ Bug Fixes * Fixes a minor issue with the regular expression used for UEFI duplicate entry cleanup which was introduced in a prior change to refactor the cleanup operation to avoid UEFI firmware which treats deletion of entries after addition as an invalid operation. * Fixes cases where duplicates may not be found in the UEFI firmware NVRAM boot entry table by explicitly looking for, and deleting for matching labels in advance of creating the EFI boot loader entry. * Fixes an issue where partitions are not visible due to a incorrect call to have the partition table re-read. * Fixes an issue where partitions are not visible due to an incorrect call to have the partition table re-read during raid configuration creation. Changes in ironic-python-agent 6.1.2..6.1.3 ------------------------------------------- dc62636 Re-read the partition table with partx -a, part 2 7438939 Re-read the partition table with partx -a e5b75d4 Fix UEFI record regex 8119040 Delete EFI boot entry duplicate labels first 0bf8769 Output verbose info from efibootmgr Diffstat (except docs and test files) ------------------------------------- ironic_python_agent/extensions/image.py | 38 ++--- ironic_python_agent/hardware.py | 2 +- .../notes/correct-uefi-regex-112211c2427cd4d9.yaml | 7 + .../de-duplicate-by-label-baa090c5b1bff992.yaml | 6 + .../notes/fix-rescan-device-7b00c6836b687ce8.yaml | 5 + .../fix-rescan-device-raid-29aa1558b036b496.yaml | 7 + 8 files changed, 208 insertions(+), 99 deletions(-)

1 0

python-tripleoclient 13.4.6 (ussuri)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

We are delighted to announce the release of: python-tripleoclient 13.4.6: TripleO client This release is part of the ussuri stable release series. The source is available from: https://opendev.org/openstack/python-tripleoclient Download the package from: https://tarballs.openstack.org/python-tripleoclient/ Please report issues through: https://bugs.launchpad.net/tripleo/+bugs For more details, please see below. Changes in python-tripleoclient 13.4.5..13.4.6 ---------------------------------------------- 731b34a4 Use netaddr when comparing local_ip for changes 0e251ff9 ctlplane network attributes in overcloud environment 1eb2a99a Use Validations libs Client for main validation entry point 71918601 [Ussuri-Only] The lower constraint file has been removed d717ee59 Don't assume json network config in validations 17b333dc make net_config_override of undercloud.conf work with yaml a06f7055 [stable/ussuri] Add support for the validations skip list feature b45e5346 Remove ipxe_enabled ppc64le validation 70dd2312 Update deployment status after upgrade converge e2fb3378 [Stable-Only]Reversing the legacy directory conditional a769ed7a Remove name parameter from cell export 6b4af194 Fetch stack after updating it 392464f1 Fix network environment validation 73f86ecb Remove deprecation warnings for the role command a4534128 Allow for cron programming of backups f7e4cdaa Add --reproduce-command option for tripleo deploy Diffstat (except docs and test files) ------------------------------------- lower-constraints.txt | 164 ------- requirements.txt | 3 +- test-requirements.txt | 1 + tox.ini | 7 - tripleoclient/config/standalone.py | 2 +- tripleoclient/constants.py | 10 +- .../v1/overcloud_deploy/test_overcloud_deploy.py | 105 ++++- .../test_overcloud_netenv_validate.py | 8 +- .../v1/overcloud_update/test_overcloud_update.py | 4 +- tripleoclient/v1/overcloud_backup.py | 22 + tripleoclient/v1/overcloud_cell.py | 13 +- tripleoclient/v1/overcloud_deploy.py | 37 ++ tripleoclient/v1/overcloud_netenv_validate.py | 2 +- tripleoclient/v1/overcloud_roles.py | 13 +- tripleoclient/v1/overcloud_upgrade.py | 15 +- tripleoclient/v1/tripleo_deploy.py | 20 + tripleoclient/v1/tripleo_validator.py | 507 ++------------------- tripleoclient/v1/undercloud_backup.py | 21 + tripleoclient/v1/undercloud_config.py | 19 +- tripleoclient/v1/undercloud_preflight.py | 18 +- 24 files changed, 431 insertions(+), 714 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index 1e8e61ef..afe356d2 100644 --- a/requirements.txt +++ b/requirements.txt @@ -21 +21,2 @@ ansible-runner>=1.4.4 # Apache 2.0 -validations-libs>=1.0.0 +validations-libs>=1.1.0 # Apache-2.0 +openstacksdk>=0.37.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 74bc779b..0d392fd6 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -13,0 +14 @@ testscenarios>=0.4 # Apache-2.0/BSD +validations-libs>=1.1.0 # Apache-2.0

1 0

nova 24.1.0 (xena)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

We are jazzed to announce the release of: nova 24.1.0: Cloud computing fabric controller This release is part of the xena 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. 24.1.0 ^^^^^^ New Features ************ * Added a new configuration option "[workarounds]/enable_qemu_monitor_announce_self" that when enabled causes the Libvirt driver to send a announce_self QEMU monitor command post live-migration. Please see bug 1815989 (https://bugs.launchpad.net/nova/+bug/1815989) for more details. Please note that this causes the domain to be considered tainted by libvirt. 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 Bug Fixes ********* * The "POST /servers" (create server) API will now reject attempts to create a server with the same port specified multiple times. This was previously accepted by the API but the instance would fail to spawn and would instead transition to the error state. * Bug #1829479 (https://bugs.launchpad.net/nova/+bug/1829479) Now deleting a nova-compute service removes allocations of successfully evacuated instances. This allows the associated resource provider to be deleted automatically even if the nova-compute service cannot recover after all instances on the node have been successfully evacuated. * 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) * Bug 1950657 (https://bugs.launchpad.net/nova/+bug/1950657) fixing behavior when nova-compute wouldn't retry image download when gets "Corrupt image download" error from glanceclient and has num_retries config option set. Changes in nova 24.0.0..24.1.0 ------------------------------ a8981422af libvirt: Add announce-self post live-migration workaround 70f75ac981 skip test_tagged_attachment in nova-next 7f6ec8cf54 Migrate RequestSpec.numa_topology to use pcpuset d860615527 Reproduce bug 1952941 d4c92bc231 api: Reject duplicate port IDs in server create a79c26e9b1 Update centos 8 py36 functional job nodeset to centos stream 8 1235dc324e [rt] Apply migration context for incoming migrations 0411962938 Extend the reproducer for 1953359 and 1952915 f0a6d946aa Reproduce bug 1953359 b44ec0dc49 Retry image download if it's corrupted 0c41bfb8c5 Add a WA flag waiting for vif-plugged event during reboot 64f5c1cfb0 Define new functional test tox env for placement gate to run 037e588788 Clean up allocations left by evacuation when deleting service 63a6388f6a Ensure MAC addresses characters are in the same case 00cba39613 Avoid unbound instance_uuid var during delete f24e0c1da2 Prevent leaked eventlets to send notifications d960c24130 Query ports with admin client to get resource_request 1066353d19 Reproduce bug 1945310 d4edcd62ba Store old_flavor already on source host during resize e6c6880465 Reproduce bug 1944759 Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 10 +- nova/api/openstack/compute/servers.py | 28 ++- nova/compute/api.py | 16 +- nova/compute/manager.py | 12 ++ nova/compute/resource_tracker.py | 35 +++- nova/conf/workarounds.py | 72 ++++++++ nova/image/glance.py | 3 +- nova/network/neutron.py | 10 +- nova/objects/instance_numa.py | 33 ++-- nova/objects/request_spec.py | 12 ++ nova/scheduler/client/report.py | 32 +++- nova/test.py | 3 + .../functional/test_servers_resource_request.py | 148 +++++++++++++++ .../unit/api/openstack/compute/test_servers.py | 33 +++- nova/virt/libvirt/driver.py | 46 ++++- nova/virt/libvirt/guest.py | 10 + nova/virt/libvirt/migration.py | 11 +- ...-self-post-live-migration-936721b1ab887514.yaml | 8 + ...reject-duplicate-port-ids-a38739d67d5d7c5d.yaml | 7 + .../notes/bug-1829479-cd2db21526965e6d.yaml | 8 + ...-event-during-hard-reboot-fb491f6a68370bab.yaml | 18 ++ ...c-numa-topology-migration-c97dbd51b3c6c116.yaml | 9 + ...-retry-corrupted-download-5798b0df44a00e4e.yaml | 7 + tox.ini | 10 + 39 files changed, 1129 insertions(+), 158 deletions(-)

1 0

nova 23.2.0 (wallaby)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

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(-)

1 0

freezer-web-ui 12.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for freezer-web-ui for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-web-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/freezer-web-ui/src/branch/stable/yoga Release notes for freezer-web-ui can be found at: https://docs.openstack.org/releasenotes/freezer-web-ui/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/openstack/freezer-web-ui and tag it *yoga-rc-potential* to bring it to the freezer-web-ui release crew's attention.

1 0

magnum-ui 10.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for magnum-ui for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/magnum-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/magnum-ui/src/branch/stable/yoga Release notes for magnum-ui can be found at: https://docs.openstack.org/releasenotes/magnum-ui/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/magnum-ui/+bugs and tag it *yoga-rc-potential* to bring it to the magnum-ui release crew's attention.

1 0

magnum 14.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for magnum for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/magnum/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/magnum/src/branch/stable/yoga Release notes for magnum can be found at: https://docs.openstack.org/releasenotes/magnum/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/magnum/+bugs and tag it *yoga-rc-potential* to bring it to the magnum release crew's attention.

1 0

freezer 12.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for freezer for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/freezer/src/branch/stable/yoga Release notes for freezer can be found at: https://docs.openstack.org/releasenotes/freezer/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/openstack/freezer and tag it *yoga-rc-potential* to bring it to the freezer release crew's attention.

1 0

nova 22.4.0 (victoria)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

We are ecstatic to announce the release of: nova 22.4.0: Cloud computing fabric controller This release is part of the victoria 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. 22.4.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 Changes in nova 22.3.0..22.4.0 ------------------------------ d54bd316b3 [rt] Apply migration context for incoming migrations 8d4487465b Extend the reproducer for 1953359 and 1952915 e549fec76f Reproduce bug 1953359 28d0059c1f Ensure MAC addresses characters are in the same case c531fdcc19 Add a WA flag waiting for vif-plugged event during reboot 34e0c0205b Store old_flavor already on source host during resize 0b1fa9b4ae Reproduce bug 1944759 Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 6 + nova/compute/manager.py | 12 ++ nova/compute/resource_tracker.py | 35 +++- nova/conf/workarounds.py | 53 ++++++ nova/virt/libvirt/driver.py | 23 ++- nova/virt/libvirt/migration.py | 11 +- ...-event-during-hard-reboot-fb491f6a68370bab.yaml | 18 ++ 11 files changed, 450 insertions(+), 10 deletions(-)

1 0

freezer-dr 12.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for freezer-dr for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-dr/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/freezer-dr/src/branch/stable/yoga Release notes for freezer-dr can be found at: https://docs.openstack.org/releasenotes/freezer-dr/

1 0

freezer-api 12.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for freezer-api for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-api/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/freezer-api/src/branch/stable/yoga Release notes for freezer-api can be found at: https://docs.openstack.org/releasenotes/freezer-api/

1 0

neutron-vpnaas 20.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for neutron-vpnaas for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-vpnaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/neutron-vpnaas/src/branch/stable/yoga Release notes for neutron-vpnaas can be found at: https://docs.openstack.org/releasenotes/neutron-vpnaas/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/neutron/+bugs and tag it *yoga-rc-potential* to bring it to the neutron-vpnaas release crew's attention.

1 0

networking-bagpipe 16.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for networking-bagpipe for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-bagpipe/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/networking-bagpipe/src/branch/stable/yoga Release notes for networking-bagpipe can be found at: https://docs.openstack.org/releasenotes/networking-bagpipe/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/networking-bagpipe/+bugs and tag it *yoga-rc-potential* to bring it to the networking-bagpipe release crew's attention.

1 0

python-watcher 8.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for python-watcher for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/watcher/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/python-watcher/src/branch/stable/yoga Release notes for python-watcher can be found at: https://docs.openstack.org/releasenotes/watcher/

1 0

neutron 20.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for neutron for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/neutron/src/branch/stable/yoga Release notes for neutron can be found at: https://docs.openstack.org/releasenotes/neutron/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/neutron/+bugs and tag it *yoga-rc-potential* to bring it to the neutron release crew's attention.

1 0

watcher-dashboard 7.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for watcher-dashboard for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/watcher-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/watcher-dashboard/src/branch/stable/yoga Release notes for watcher-dashboard can be found at: https://docs.openstack.org/releasenotes/watcher-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/watcher-dashboard/+bugs and tag it *yoga-rc-potential* to bring it to the watcher-dashboard release crew's attention.

1 0

ovn-octavia-provider 2.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for ovn-octavia-provider for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/ovn-octavia-provider/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/ovn-octavia-provider/src/branch/stable/yoga Release notes for ovn-octavia-provider can be found at: https://docs.openstack.org/releasenotes/ovn-octavia-provider/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/neutron/+bugs and tag it *yoga-rc-potential* to bring it to the ovn-octavia-provider release crew's attention.

1 0

networking-bgpvpn 16.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for networking-bgpvpn for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-bgpvpn/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/networking-bgpvpn/src/branch/stable/yoga Release notes for networking-bgpvpn can be found at: https://docs.openstack.org/releasenotes/networking-bgpvpn/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/bgpvpn/+bugs and tag it *yoga-rc-potential* to bring it to the networking-bgpvpn release crew's attention.

1 0

designate-dashboard 14.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for designate-dashboard for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/designate-dashboard/src/branch/stable/yoga Release notes for designate-dashboard can be found at: https://docs.openstack.org/releasenotes/designate-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/designate-dashboard/+bugs and tag it *yoga-rc-potential* to bring it to the designate-dashboard release crew's attention.

1 0

kuryr-libnetwork 9.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for kuryr-libnetwork for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kuryr-libnetwork/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/kuryr-libnetwork/src/branch/stable/yoga Release notes for kuryr-libnetwork can be found at: https://docs.openstack.org/releasenotes/kuryr-libnetwork/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/kuryr-libnetwork/+bugs and tag it *yoga-rc-potential* to bring it to the kuryr-libnetwork release crew's attention.

1 0

trove 17.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for trove for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/trove/src/branch/stable/yoga Release notes for trove can be found at: https://docs.openstack.org/releasenotes/trove/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/trove/+bugs and tag it *yoga-rc-potential* to bring it to the trove release crew's attention.

1 0

manila-ui 7.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for manila-ui for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/manila-ui/src/branch/stable/yoga Release notes for manila-ui can be found at: https://docs.openstack.org/releasenotes/manila-ui/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/manila-ui/+bugs and tag it *yoga-rc-potential* to bring it to the manila-ui release crew's attention.

1 0

tap-as-a-service 9.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for tap-as-a-service for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tap-as-a-service/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/tap-as-a-service/src/branch/stable/yoga Release notes for tap-as-a-service can be found at: https://docs.openstack.org/releasenotes/tap-as-a-service/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/tap-as-a-service/+bugs and tag it *yoga-rc-potential* to bring it to the tap-as-a-service release crew's attention.

1 0

trove-dashboard 18.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for trove-dashboard for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/trove-dashboard/src/branch/stable/yoga Release notes for trove-dashboard can be found at: https://docs.openstack.org/releasenotes/trove-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/trove-dashboard/+bugs and tag it *yoga-rc-potential* to bring it to the trove-dashboard release crew's attention.

1 0

openstack-placement 7.0.0.0rc1 (yoga)
by no-reply＠openstack.org 10 Mar '22

10 Mar '22

Hello everyone, A new release candidate for openstack-placement for the end of the Yoga cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/placement/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Yoga release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/yoga release branch at: https://opendev.org/openstack/openstack-placement/src/branch/stable/yoga Release notes for openstack-placement can be found at: https://docs.openstack.org/releasenotes/placement/

1 0