Comment 6 for bug 1956846

Maximilian,

I have looked at this further, and I think if you specify 'proto boot' or 'proto
3' it should do what you want.

If you execute 'ip -d route show' you should see that the default proto is boot.
See keepalived commit edd8326 to see what the old code did.

On Mon, 2022-01-10 at 18:46 +0000, Maximilian Stinsky wrote:
> The workaround we tested as mentioned in comment #1 is sadly not working as
> the `protocol 0` in the keepalived.conf is still a protocol so we end up with
> duplicated routes anyway.
> e.g.:
> default via x.x.244.67 dev qg-6c2ee5e0-ad proto unspec
> default via x.x.244.67 dev qg-6c2ee5e0-ad
>
>
> The question now for us is, is there an easy "workaround" way to get neutron
> stein working with keepalived >= 2.0.1.
> @Rodolfo we were thinking about removing the virtual_route part from the
> keepalived config until we can upgrade to train. Our assumption is that
> neutron is already managing all the routes when failing over. Is there any
> particular reason the virtual_routes are needed inside keepalived?
>