Comment 11 for bug 1956846

Rudolfo,

When I was looking at the keepalived code in Neutron, I noticed a reference to keepalived bugs [1]. If there are any bugs in keepalived that are detrimental to Neutron, it would be helpful if they could be reported at https://github.com/acassen/keepalived/issues so that we can endeavour to fix them.

What is described at [1] is very strange, and the workaround seems quite problematic to me. I am not aware what keepalived bugs are being referred to, and I am not aware of a problem if the "primary VIP" is changed on a reload, but if there is a problem we will fix it. It seems quite strange to me, and problematic, that Neutron should make up and configure an additional address, which could very easily be used by another device on the network, and then allow keepalived to configure that address on the system, potentially thereby causing a duplicate address on the network.

Can we work together to try and sort out what is happening here, since it doesn't feel right to me. I will happily work to resolve any bugs identified in keepalived.

[1]https://github.com/openstack/neutron/blob/master/neutron/agent/linux/keepalived.py#L273-L278