So I was doing some testing and this looks like it will happen very quickly
after an agent restarts.
The rule priorities are stored as a set and are allocated from by calling
.pop(). In local testing, it looks like that pretty consistently pulls the
first priority off of the range.
On 4 May 2016 at 14:26, Assaf Muller wrote:
> On Wed, May 4, 2016 at 4:54 PM, Kevin Benton wrote:
> > Hello,
> >
> > I would like to propose a freeze exception for
> > https://review.openstack.org/#/c/312253/ and
> > https://review.openstack.org/#/c/312254/ .
On Wed, May 4, 2016 at 4:54 PM, Kevin Benton wrote:
> Hello,
>
> I would like to propose a freeze exception for
> https://review.openstack.org/#/c/312253/ and
> https://review.openstack.org/#/c/312254/ . They address a bug in DVR that
> causes floating IPs to eventually break
Hello,
I would like to propose a freeze exception for
https://review.openstack.org/#/c/312253/ and
https://review.openstack.org/#/c/312254/ . They address a bug in DVR that
causes floating IPs to eventually break after an L3 agent has been
restarted. It's a serious bug but it's very subtle