5dfe116dac
Lots of bug fixes but nothing I'd consider require
a minor version bump.
$ git log --oneline --no-merges --no-decorate 17.0.10..
9cbd2aedde fix up numa-topology live migration hypervisor check
9999bce00f Fail to live migration if instance has a NUMA topology
ab445a027a Allow driver to properly unplug VIFs on destination on confirm resize
8519b1ce6d Move get_pci_mapping_for_migration to MigrationContext
d3bdeb2615 libvirt: Do not reraise DiskNotFound exceptions during resize
2009859b52 Include all network devices in nova diagnostics
20b90f2e26 Workaround missing RequestSpec.instance_group.uuid
581df2c986 Add regression recreate test for bug 1830747
95a3e0cf6a Restore connection_info after live migration rollback
88fd40fe5d DRY up test_rollback_live_migration_set_migration_status
58a140487c Block swap volume on volumes with >1 rw attachment
55deddf65d Fix live-migration when glance image deleted
944b24f462 Add functional confirm_migration_error test
5600309a1f [stable-only] Delete allocations even if _confirm_resize raises (part 2)
b8435d6001 Delete allocations even if _confirm_resize raises
0cad3089d3 Stop logging traceback when skipping quiesce
f9c2503609 Fix retry of instance_update_and_get_original
89063ecb61 Teardown networking when rolling back live migration even if shared disk
01141392db Use migration_status during volume migrating and retyping
99a63a6633 libvirt: Always disconnect volumes after libvirtError exceptions
63b45a87b8 libvirt: Stop ignoring unknown libvirtError exceptions during volume attach
ba3ad2d65a Fix {min|max}_version in ironic Adapter setup
22cd12dbb7 Create request spec, build request and mappings in one transaction
5b0adaa0ca xenapi/agent: Change openssl error handling
ec43a1348d libvirt: Avoid using os-brick encryptors when device_path isn't provided
899e881b18 Fix nova-grenade-live-migration run book for opendev migration
d4dbbb645a Fix regression in glance client call
1cee746085 OpenDev Migration Patch
76418a32cb Move legacy-grenade-dsvm-neutron-multinode-live-migration in-tree
5d5e7be8cb Fix legacy-grenade-dsvm-neutron-multinode-live-migration
c8ad9f4e19 libvirt: set device address tag only if setting disk unit
ee52fb12bb libvirt: disconnect volume when encryption fails
5433dc6a75 Add missing libvirt exception during device detach
c6a42cd3b3 Error out migration when confirm_resize fails
f1554d1b52 prevent common kwargs from glance client failure
dba9b722af Define irrelevant-files for tempest-full-py3 job
1b6f48354b Delete instance_id_mappings record in instance_destroy
8f1773a7af Do not persist RequestSpec.ignore_hosts
9fd4082d7c Add functional regression test for bug 1669054
99cbbcfd61 Update instance.availability_zone on revertResize
1b15a342e3 Add functional recreate test for bug 1819963
50a0c6a4b9 [Stable Only] hardware: Handle races during pinning
ddc2c9118a Fix incomplete instance data returned after build failure
ee07c1c67d Update instance.availability_zone during live migration
36d93675d9 Update resources once in update_available_resource
705284e18c Don't persist zero allocation ratios in ResourceTracker
7a3b072442 Document unset/reset wrinkle for *_allocation_ratio options
1265e9e8e2 Replace openstack.org git:// URLs with https://
4a7575bf14 Ignore VolumeAttachmentNotFound exception in compute.manager
Change-Id: Ife5d3a108a9ef566cbbd42a00b4859c240d77e64
Using This Repository
All official OpenStack software should go through the 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).
This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.
The repository is managed by the Release Management team.
Refer to the reference documentation for more details
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.