Hi Dumitru,
thanks for the review. I’ve addressed requested changes in v2:
https://patchwork.ozlabs.org/project/ovn/patch/20220131173457.64391-1-odiv...@gmail.com/
Regards,
Vladislav Odintsov
> On 28 Jan 2022, at 20:06, Dumitru Ceara wrote:
>
> On 1/28/22 18:04, Dumitru Ceara wrote:
>> On
On 1/28/22 18:04, Dumitru Ceara wrote:
> On 1/24/22 12:30, Vladislav Odintsov wrote:
>> After commit [0] the mandatory vtep chassis's option 'is-vtep' has appeared.
>> The upgrade scenario for ovn-controller-vtep was not supported:
>> 'is-vtep' option was set only on vtep chassis creation. If
On 1/24/22 12:30, Vladislav Odintsov wrote:
> After commit [0] the mandatory vtep chassis's option 'is-vtep' has appeared.
> The upgrade scenario for ovn-controller-vtep was not supported:
> 'is-vtep' option was set only on vtep chassis creation. If chassis was
> created prior to a new codebase,
After commit [0] the mandatory vtep chassis's option 'is-vtep' has appeared.
The upgrade scenario for ovn-controller-vtep was not supported:
'is-vtep' option was set only on vtep chassis creation. If chassis was
created prior to a new codebase, it was left intact and HW VTEP connectivity
was
