On Fri, Feb 21, 2020 at 1:03 AM Russell Bryant wrote:
>
> On Thu, Feb 20, 2020 at 10:46 AM Numan Siddique wrote:
>
> > On Wed, Feb 19, 2020 at 9:27 PM Russell Bryant wrote:
> > >
> > > We recently hit a bug in ovn-kubernetes, where I accidentally added
> > > /64 at the end of ipv6_prefix, to mat
On Thu, Feb 20, 2020 at 10:46 AM Numan Siddique wrote:
> On Wed, Feb 19, 2020 at 9:27 PM Russell Bryant wrote:
> >
> > We recently hit a bug in ovn-kubernetes, where I accidentally added
> > /64 at the end of ipv6_prefix, to match the format we used for the
> > subnet option for IPv4. This was
On Wed, Feb 19, 2020 at 9:27 PM Russell Bryant wrote:
>
> We recently hit a bug in ovn-kubernetes, where I accidentally added
> /64 at the end of ipv6_prefix, to match the format we used for the
> subnet option for IPv4. This was not allowed.
>
> This patch update ovn-northd to take the ipv6_pref
Bleep bloop. Greetings Russell Bryant, 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.
checkpatch:
WARNING: Line is 82 characters long (recommended limit is 79)
#41 FILE: northd/ovn-northd.c:6
We recently hit a bug in ovn-kubernetes, where I accidentally added
/64 at the end of ipv6_prefix, to match the format we used for the
subnet option for IPv4. This was not allowed.
This patch update ovn-northd to take the ipv6_prefix either with or
without a trailing "/64". It still enforces a /
