Do not block connection between br-int and br-phys on startup
Block traffic between br-int and br-physical is over kill
and will at least
1. interrupt vlan flow during startup, and is particularly
so if dvr enabled
2. if let's rabbitmq is not stable, it is possible data plane
will be affected and vlan will never work.
Using openstack on k8s particularly amplifies the problem
because pod could be killed pretty easily by liveness
probes.
Reviewed: https:/ /review. opendev. org/738512 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=131bbc9a534 11033cf27664d8f 1fd7afc72c57bf
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 131bbc9a5341103 3cf27664d8f1fd7 afc72c57bf
Author: shenjiatong <email address hidden>
Date: Thu Jun 18 15:33:13 2020 +0800
Do not block connection between br-int and br-phys on startup
Block traffic between br-int and br-physical is over kill
and will at least
1. interrupt vlan flow during startup, and is particularly
so if dvr enabled
2. if let's rabbitmq is not stable, it is possible data plane
will be affected and vlan will never work.
Using openstack on k8s particularly amplifies the problem
because pod could be killed pretty easily by liveness
probes.
Conflicts:
neutron/ plugins/ ml2/drivers/ openvswitch/ agent/ovs_ neutron_ agent.py
Change-Id: I51050c600ba709 0fea71213687d94 340bac0674a 2d811997ebba699 cab431d696)
Closes-Bug: #1869808
(cherry picked from commit 90212b12cdf62e9