Did I get the situation (with all the provided background) correct:
So, if setup rpc first, the rabbit gets muted and rpc cannot be checked before setting up bridges (no rules matching in secure mode - no flow).
And if setup bridges first, it blocks on rpc and no blocking rules got installed on bridges that causes ~1 mil/s packets arp storm.
Ultimately with the blocking rule (being removed in https://review.opendev.org/#/c/733568/), there is a dataplane downtime each time the neutron ovs agent restarted?
If so, the only solution I can think of (after reverting the latter patch) is make rpc check and the setup bridges to be exec'ed *real* parallel, and added a strict timeouts + a single retry for each of it?
Did I get the situation (with all the provided background) correct:
So, if setup rpc first, the rabbit gets muted and rpc cannot be checked before setting up bridges (no rules matching in secure mode - no flow).
And if setup bridges first, it blocks on rpc and no blocking rules got installed on bridges that causes ~1 mil/s packets arp storm.
Ultimately with the blocking rule (being removed in https:/ /review. opendev. org/#/c/ 733568/), there is a dataplane downtime each time the neutron ovs agent restarted?
If so, the only solution I can think of (after reverting the latter patch) is make rpc check and the setup bridges to be exec'ed *real* parallel, and added a strict timeouts + a single retry for each of it?