neutron: handle binding:profile=None during migration
The port binding:profile handling in _setup_migration_port_profile
and _update_port_binding_for_instance is not handling when the
binding:profile is set on the port but the value is None, which
results in a NoneType error. Neutron API does not define a format
for this field, or whether or not it will be specified on the port,
and if so, if it's an empty dict or None, so let's be safe and
make sure we handle None.
Because of how many places we access the binding:profile on
a port, this adds a common helper utility.
Co-Authored-By: Eric M Gonzalez <email address hidden>
Change-Id: I564bac88fad6cc47ccbf7425b1ab39899fdc1c2e
Closes-Bug: #1717365
(cherry picked from commit 8ac7be36bedaf0dd3467efc5b5bffdb365b8231b)
(cherry picked from commit c393e490751416f408432ec20e2b1afc1af88af0)
Reviewed: https:/ /review. openstack. org/506320 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=b2577207203 167d7b8610531be df0f480a9b7865
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit b2577207203167d 7b8610531bedf0f 480a9b7865
Author: Matt Riedemann <email address hidden>
Date: Thu Sep 14 18:04:20 2017 -0400
neutron: handle binding: profile= None during migration
The port binding:profile handling in _setup_ migration_ port_profile port_binding_ for_instance is not handling when the
and _update_
binding:profile is set on the port but the value is None, which
results in a NoneType error. Neutron API does not define a format
for this field, or whether or not it will be specified on the port,
and if so, if it's an empty dict or None, so let's be safe and
make sure we handle None.
Because of how many places we access the binding:profile on
a port, this adds a common helper utility.
Co-Authored-By: Eric M Gonzalez <email address hidden>
Change-Id: I564bac88fad6cc 47ccbf7425b1ab3 9899fdc1c2e d3467efc5b5bffd b365b8231b) 408432ec20e2b1a fc1af88af0)
Closes-Bug: #1717365
(cherry picked from commit 8ac7be36bedaf0d
(cherry picked from commit c393e490751416f