In patch [1] there was added usage of context parameter in method
get_vif_type in openvswitch mech_driver.
This exposed that previously "wrong" context was passed to this method
in _update_segmentation_id() method in ml2 plugin and that caused
raising AttributeError as "Context" object didn't have attribute
'current'.
This patch adds new method "get_supported_vif_type" to mechanism
drivers and this method don't need context to return what vif_types
are supported regarding agent type.
Reviewed: https:/ /review. opendev. org/665548 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=352f5ac674d de0d76ebe92d80b 2cb02638b80ade
Committed: https:/
Submitter: Zuul
Branch: master
commit 352f5ac674dde0d 76ebe92d80b2cb0 2638b80ade
Author: Slawek Kaplonski <email address hidden>
Date: Fri Jun 14 10:35:46 2019 +0200
Fix update of network's segmentation id
In patch [1] there was added usage of context parameter in method segmentation_ id() method in ml2 plugin and that caused
get_vif_type in openvswitch mech_driver.
This exposed that previously "wrong" context was passed to this method
in _update_
raising AttributeError as "Context" object didn't have attribute
'current'.
This patch adds new method "get_supported_ vif_type" to mechanism
drivers and this method don't need context to return what vif_types
are supported regarding agent type.
[1] https:/ /review. opendev. org/#/c/ 658784/
Change-Id: Ic6c738db28208e 5009f78bb52598e b3c141f639f
Related-Bug: #1832985