vs-dev@openvswitch.org
> ; Ankur Sharma
> Subject: Re: [ovs-dev] [PATCH v1] ovn-controller: Fix the CT zone assignment
> logic for logical routers
>
> On 8/4/20 5:55 AM, Ankur Sharma wrote:
>> From: Ankur Sharma
>>
>> BACKGROUND:
>> a. ovn-cont
@openvswitch.org
; Ankur Sharma
Subject: Re: [ovs-dev] [PATCH v1] ovn-controller: Fix the CT zone assignment
logic for logical routers
On 8/4/20 5:55 AM, Ankur Sharma wrote:
> From: Ankur Sharma
>
> BACKGROUND:
> a. ovn-controller assigns CT ZONES for local ports and datapaths.
> b.
On 8/4/20 5:55 AM, Ankur Sharma wrote:
> From: Ankur Sharma
>
> BACKGROUND:
> a. ovn-controller assigns CT ZONES for local ports and datapaths.
> b. If a local port/datapath is cleaned up from a chassis, then
>corresponding CT ZONE is "unassigned"/"freed" up.
>
> ISSUE:
> Above logic and imp
Bleep bloop. Greetings Ankur Sharma, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
git-am:
error: sha1 information is lacking or useless (controller/ovn-controller.c).
error: could not build
From: Ankur Sharma
BACKGROUND:
a. ovn-controller assigns CT ZONES for local ports and datapaths.
b. If a local port/datapath is cleaned up from a chassis, then
corresponding CT ZONE is "unassigned"/"freed" up.
ISSUE:
Above logic and implementations leaves stale CT entries in the
datapath, whi
