Comment 6 for bug 1688155

Thanks for the above information. Do you know if this issue will happen with even just a single controller node? The reason I ask is this. If you have only a single node and this issue still occurs it is because OVS doesn't persist its configuration through node restart, which I would think is an OVS bug. If on the other hand it only happens with multiple nodes it may be because the manila service comes up on a new Controller mode (as it would normally if you have pacemaker control of Controller node services like manila share) and the integration bridge on the new node was never set up by manila share in the first place.