0a067698da
$ git log --oneline --no-merges 19.3.0..HEAD 6007c41aa8 compute: Don't delete the original attachment during pre LM rollback 06d9d0d705 Add regression tests for bug #1889108 07a04ee171 compute: refactor volume bdm rollback error handling 334a479ae2 libvirt: Do not reference VIR_ERR_DEVICE_MISSING when libvirt is < v4.1.0 76428c1a6a libvirt: Handle VIR_ERR_DEVICE_MISSING when detaching devices 8b865378b8 compute: Use source_bdms to reset attachment_ids during LM rollback 1e1bbdc4cd Robustify attachment tracking in CinderFixtureNewAttachFlow f81d1a5ce4 Improve CinderFixtureNewAttachFlow b9ea91d177 libvirt: Provide VIR_MIGRATE_PARAM_PERSIST_XML during live migration 33c8e5473d Should not skip volume_size check for bdm.image_id == image_ref case 0bc5a4ecb5 objects: Update keypairs when saving an instance Change-Id: I8cd760ac32877748eb2e933a80cd0491ffb19334
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.