On Thu, Nov 15, 2018 at 11:31 AM Ben Pfaff <[email protected]> wrote: > > On Thu, Nov 15, 2018 at 11:07:11AM -0800, Han Zhou wrote: > > From: Han Zhou <[email protected]> > > > > When adding a new chassis, if there is an old chassis with same IP > > existed in Encap table, it is allowed to be added today. However, > > allowing it to be added results in problems: > > > > 1. The new chassis cannot work because none of the other chassises > > are able to create tunnel to it, because of the IP confliction > > with already existed tunnel to the old chassis. > > > > 2. All the other chassises will continuously retry creating the tunnel > > and complaining about the error. > > > > So, instead of hiding the problem, it is better to expose it while > > trying to add the second chassis with duplicated IP. This patch > > ensures it from the ovsdb schema. > > > > Signed-off-by: Han Zhou <[email protected]> > > --- > > v2 -> v3: update NEWS for the potential DB upgrading failure > > Thanks a lot for adding some upgrade information. > > It's probably better to put detailed information like this for OVN > upgrades in Documentation/intro/install/ovn-upgrades.rst. Then NEWS > could point to that advice. > > Thanks, > > Ben.
Makes sense! Please check v4: https://mail.openvswitch.org/pipermail/ovs-dev/2018-November/353981.html _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
