[ovs-dev] [PATCH v2 ovn 2/2] chassis: Fix chassis_private record updates when the system-id changes.
numans at ovn.org
Fri Sep 4 14:36:57 UTC 2020
On Fri, Sep 4, 2020 at 7:26 PM Dumitru Ceara <dceara at redhat.com> wrote:
> On 9/4/20 3:52 PM, Numan Siddique wrote:
> > On Thu, Sep 3, 2020 at 8:34 PM Dumitru Ceara <dceara at redhat.com
> > <mailto:dceara at redhat.com>> wrote:
> > Also:
> > - Change conditional monitoring for Chassis_Private to use the
> > chassis uuid
> > instead of chassis name. Using the chassis->name field does not
> > because this is the old value of the field and would cause
> > ovsdb-server
> > to inform ovn-controller that the updated Chassis_Private record
> > "deleted" because it doesn't match the monitor condition anymore.
> > - Allow ovn-sbctl to access Chassis_Private records by name.
> > Reported-at: https://bugzilla.redhat.com/1873032
> > Reported-by: Ying Xu <yinxu at redhat.com <mailto:yinxu at redhat.com>>
> > CC: Han Zhou <hzhou at ovn.org <mailto:hzhou at ovn.org>>
> > Fixes: 4adc10f58127 ("Avoid nb_cfg update notification flooding")
> > Signed-off-by: Dumitru Ceara <dceara at redhat.com
> > <mailto:dceara at redhat.com>>
> > ---
> > v2:
> > - Fix the monitor condition update reported by Numan.
> > Thanks Dumitru. I applied both the patches to master.
> > Numan
> Thanks Numan!
> Patch 1/2 should apply cleanly to branch20.06 too. Would it be possible
> to backport it there too?
Ok. I backported patch 1 to branch-20.06.
> For branch20.03 I can send a separate backport patch if you think that's
Feel free to submit the patch against branch-20.03 if you think it's
required. I'm fine backporting it.
> dev mailing list
> dev at openvswitch.org
More information about the dev