When starting up, we don't want to delete the patch port between br-int
and br-tun unless we're also dropping the flows.. In liberty both of
these bridges were switched to not dump flows on startup and to put the
bridges in secure mode so that default flood flows are not installed
when the bridge is created.
Without this patch the patch port is torn down and not reinstalled until
br-tun is setup again.
Partial-Bug: #1514056
Change-Id: Ia518a99a2de5d1bda467fde57892c43970f88bcd
(cherry picked from commit 8dce6a5c873c2c18e5a9c6165bf3974aead02588)
Reviewed: https:/ /review. openstack. org/299280 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=b392ad1c66d feb4d0954fae3c5 170381ff1bdef0
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit b392ad1c66dfeb4 d0954fae3c51703 81ff1bdef0
Author: Clayton O'Neill <email address hidden>
Date: Thu Mar 24 14:59:41 2016 +0000
Don't delete br-int to br-tun patch on startup
When starting up, we don't want to delete the patch port between br-int
and br-tun unless we're also dropping the flows.. In liberty both of
these bridges were switched to not dump flows on startup and to put the
bridges in secure mode so that default flood flows are not installed
when the bridge is created.
Without this patch the patch port is torn down and not reinstalled until
br-tun is setup again.
Partial-Bug: #1514056 bda467fde57892c 43970f88bcd 8e5a9c6165bf397 4aead02588)
Change-Id: Ia518a99a2de5d1
(cherry picked from commit 8dce6a5c873c2c1