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.
Change-Id: I51050c600ba7090fea71213687d94340bac0674a
Closes-Bug: #1869808
(cherry picked from commit 90212b12cdf62e92d811997ebba699cab431d696)
Reviewed: https:/ /review. opendev. org/738504 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=4f501f405d1 c44e00784df8450 cbe83129da1ea7
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit 4f501f405d1c44e 00784df8450cbe8 3129da1ea7
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.
Change-Id: I51050c600ba709 0fea71213687d94 340bac0674a 2d811997ebba699 cab431d696)
Closes-Bug: #1869808
(cherry picked from commit 90212b12cdf62e9