- Release-announce - lists.openstack.org

masakari 9.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

masakari-dashboard 2.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

designate 10.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

kuryr-kubernetes 2.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

designate-dashboard 10.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

Hello everyone, A new release candidate for designate-dashboard for the end of the Ussuri 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 Ussuri release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/ussuri release branch at: https://opendev.org/openstack/designate-dashboard/src/branch/stable/ussuri 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 *ussuri-rc-potential* to bring it to the designate-dashboard release crew's attention.

1 0

storlets 5.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

nova 20.2.0 (train)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

We high-spiritedly announce the release of: nova 20.2.0: Cloud computing fabric controller This release is part of the train 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. 20.2.0 ^^^^^^ Bug Fixes * This release contains a fix for a regression introduced in 15.0.0 (Ocata) where server create failing during scheduling would not result in an instance action record being created in the cell0 database. Now when creating a server fails during scheduling and is "buried" in cell0 a "create" action will be created with an event named "conductor_schedule_and_build_instances". (https://bugs.launchpad.net/nova/+bug/1852458) * This release contains a fix for bug 1856925 such that "resize" and "migrate" server actions will be rejected with a 409 "HTTPConflict" response if the source compute service is down. (https://bugs.launchpad.net/nova/+bug/1856925) * The Compute service has never supported direct booting of an instance from an image that was created by the Block Storage service from an encrypted volume. Previously, this operation would result in an ACTIVE instance that was unusable. Beginning with this release, an attempt to boot from such an image will result in the Compute API returning a 400 (Bad Request) response. * A new config option "[neutron]http_retries" is added which defaults to 3. It controls how many times to retry a Neutron API call in response to a HTTP connection failure. An example scenario where it will help is when a deployment is using HAProxy and connections get closed after idle time. If an incoming request tries to re-use a connection that is simultaneously being torn down, a HTTP connection failure will occur and previously Nova would fail the entire request. With retries, Nova can be more resilient in this scenario and continue the request if a retry succeeds. Refer to https://launchpad.net/bugs/1866937 for more details. Changes in nova 20.1.1..20.2.0 ------------------------------ 240d030902 Reject boot request for unsupported images 923a4f9be6 Avoid spurious error logging in _get_compute_nodes_in_db 6fa8540f2c Abort live-migration during instance_init 03fd4ac755 libvirt: Calculate disk_over_committed for raw instances 6749bad463 Use placement stable version for functional job 88205a4e91 Reset the cell cache for database access in Service 71971c2062 Add config option for neutron client retries b08d59ac7b bug-fix: Reject live migration with vpmem 91d410b92f nova-live-migration: Ensure subnode is fenced during evacuation testing 70447bca2f nova-live-migration: Wait for n-cpu services to come up after configuring Ceph 588b0484bf Lowercase ironic driver hash ring and ignore case in cache c48d621843 Fix intermittently failing regression case 93f903d794 Fix os-keypairs pagination links 2f4e3ac3b0 Fix hypervisors paginted collection_name. e6b749dbdd Clean up allocation if unshelve fails due to neutron bd1bfc13d7 Reproduce bug 1862633 3e935325a8 Unplug VIFs as part of cleanup of networks 24600430a2 Functional test for UnexpectedDeletingTaskStateError 73d9b6e5f6 libvirt: Ignore DiskNotFound during update_available_resource 7fd41e9b8c libvirt: Provide the backing file format when creating qcow2 disks 09059de8a9 Recalculate 'RequestSpec.numa_topology' on resize 03d59e2893 Make RBD imagebackend flatten method idempotent 52426cb15d Set instance CPU policy to 'share' through image property 938b499b1f Ensure source service is up before resizing/migrating 48f9b1c2ce Print help if nova-manage subcommand is not specified 6484d9ff5b Create instance action when burying in cell0 7d7a3ba70a libvirt: avoid cpu check at s390x arch Diffstat (except docs and test files) ------------------------------------- .../keypairs/v2.35/keypairs-list-resp.json | 4 +- .../keypairs/v2.35/keypairs-list-user2-resp.json | 4 +- .../v2.33/hypervisors-detail-resp.json | 2 +- .../v2.33/hypervisors-list-resp.json | 2 +- .../v2.53/hypervisors-detail-resp.json | 2 +- .../v2.53/hypervisors-list-resp.json | 2 +- gate/live_migration/hooks/ceph.sh | 47 +++++++- gate/test_evacuate.sh | 5 + nova/api/openstack/compute/migrate_server.py | 6 +- nova/api/openstack/compute/servers.py | 14 ++- nova/api/openstack/compute/views/hypervisors.py | 2 +- nova/api/openstack/compute/views/keypairs.py | 2 +- nova/cmd/common.py | 1 + nova/compute/api.py | 114 ++++++++++++++----- nova/compute/manager.py | 105 +++++++++++++++--- nova/conductor/manager.py | 27 +++++ nova/conductor/tasks/live_migrate.py | 17 +++ nova/conf/neutron.py | 14 +++ nova/context.py | 3 - nova/network/neutronv2/api.py | 3 +- nova/objects/instance.py | 4 + nova/service.py | 37 ++++++- .../keypairs/v2.35/keypairs-list-resp.json.tpl | 2 +- .../v2.35/keypairs-list-user2-resp.json.tpl | 2 +- .../v2.33/hypervisors-detail-resp.json.tpl | 2 +- .../v2.33/hypervisors-list-resp.json.tpl | 2 +- .../v2.53/hypervisors-detail-resp.json.tpl | 2 +- .../v2.53/hypervisors-list-resp.json.tpl | 2 +- .../functional/regressions/test_bug_1831771.py | 102 +++++++++++++++++ .../functional/regressions/test_bug_1852458.py | 82 ++++++++++++++ .../functional/regressions/test_bug_1862633.py | 95 ++++++++++++++++ .../openstack/compute/admin_only_action_common.py | 8 +- .../unit/api/openstack/compute/test_hypervisors.py | 12 +- .../api/openstack/compute/test_migrate_server.py | 6 +- .../api/openstack/compute/test_server_actions.py | 6 +- .../unit/api/openstack/compute/test_serversV21.py | 16 +++ .../unit/conductor/tasks/test_live_migrate.py | 14 +++ nova/virt/driver.py | 3 - nova/virt/hardware.py | 2 +- nova/virt/ironic/driver.py | 7 +- nova/virt/libvirt/driver.py | 51 ++++----- nova/virt/libvirt/imagebackend.py | 12 +- nova/virt/libvirt/utils.py | 3 +- ...458-cell0-instance-action-e3112cf17bcc7c64.yaml | 11 ++ ...eck-source-compute-resize-16e9c3b24cf72301.yaml | 8 ++ ...-detect-nonbootable-image-6fad7f865b45f879.yaml | 9 ++ ...eutron-connection-retries-c276010afe238abc.yaml | 12 ++ tox.ini | 23 ++-- 65 files changed, 1516 insertions(+), 222 deletions(-)

1 0

networking-odl 16.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

congress-dashboard 6.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0

openstack-congress 11.0.0.0rc1 (ussuri)
by no-reply＠openstack.org 23 Apr '20

23 Apr '20

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

1 0