86ad3cb242
As part of resolving bug #1734320 the os-vif ovs plugin was modified to always plug the vif to ovs in all code paths. This change reverts that behavior as it has been determined that libvirt will recreate the port which introduces new issues for neutron and breaks the intent of the os-vif change. Change-Id: I76a2de2e8077d8a931af0056690dad4a569e228a Related-Bug: #1728600 Related-Bug: #1808171 Related-Bug: #1811405
18 lines
981 B
YAML
18 lines
981 B
YAML
---
|
|
security:
|
|
- |
|
|
In 1.13.0 it was reported that bug #1734320 was partially resolved by
|
|
change Iaf15fa7a678ec2624f7c12f634269c465fbad930. It has since emerged
|
|
that that change introduced another bug due to an interaction with
|
|
libvirt. It was understood that libvirt would not recreate the ovs port
|
|
if it was present on the ovs bridge when spawning a vm however on
|
|
inspection of the libvirt code this is not the case. In this release
|
|
we have reverted the change to os-vif and libvirt will be the only
|
|
entity to create the ovs port when vif_type is set to ovs and
|
|
hybrid_plug is set to false in the neutron port binding details.
|
|
Bug #1734320 is not expected to be present if hybrid_plug=true or
|
|
vif_type vhost-user is used on linux. On windows if hybrid_plug is false
|
|
on bug #1734320 is also not expected to be present. A new mitigation to
|
|
bug #1734320 will be developed for the remaining case of
|
|
hybrid_plug=false on linux.
|