b8f3be6b3c
In the rocky cycle nova was enhanced to support the multiple port binding live migration workflow when neutron supports the binding-extended API extension. When the migration_data object was extended to support multiple port bindings, populating the vifs field was used as a sentinel to indicate that the new workflow should be used. In the train release I734cc01dce13f9e75a16639faf890ddb1661b7eb (SR-IOV Live migration indirect port support) broke the semantics of the migrate_data object by unconditionally populating the vifs field This change restores the rocky semantics, which are depended on by several parts of the code base, by only conditionally populating vifs if neutron supports multiple port bindings. Co-Authored-By: Sean Mooney <work@seanmooney.info> Change-Id: Ia00277ac8a68a635db85f9e0ce2c6d8df396e0d8 Closes-Bug: #1888395
15 lines
778 B
YAML
15 lines
778 B
YAML
---
|
|
fixes:
|
|
- |
|
|
In the Rocky (18.0.0) release support was added to nova to use neutron's
|
|
multiple port binding feature when the binding-extended API extension
|
|
is available. In the Train (20.0.0) release the SR-IOV live migration
|
|
feature broke the semantics of the vifs field in the ``migration_data``
|
|
object that signals if the new multiple port binding workflow should
|
|
be used by always populating it even when the ``binding-extended`` API
|
|
extension is not present. This broke live migration for any deployment
|
|
that did not support the optional ``binding-extended`` API extension.
|
|
The Rocky behavior has now been restored enabling live migration
|
|
using the single port binding workflow when multiple port bindings
|
|
are not available.
|