-
-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating link or setting interface up with unicast_src before address assigned to i/f doesn't work #1847
Comments
Hi Quentin - Could this issue also be the reason, that the Having the option set in my VRRP instance and removing the src ip using |
@jeppech Could you please provide a copy of your configuration and the output of |
@pqarmitage Sure! - Also, I'd might as well give some info about my setup: Keepalived is installed on 2 VPSs, on Hetzner. One node is MASTER(node1), the other is BACKUP(node2). They're communicating using Hetzners private cloud network. Both nodes are configured with a If I log on to
Re-assigning the LAN IP on
This leaves the nodes in kind of a split brain scenario. keepalived version
ip addr show [node2]
/etc/keepalived/keepalived.conf [node1]
/etc/keepalived/keepalived.conf [node2]
|
Describe the bug
Setting an interface up without the unicast_src configured on the interface means that keepalived cannot bind to the unicast_src and so doesn't receive adverts from other nodes; however the VRRP instance is not put into fault state, and so it transitions to master, even if there is a higher priority master. Subsequently adding the unicast_src IP makes it work again.
Deleting an interface and subsequently recreating it causes a bind error which is not detected. The VRRP instance then does not work again
Deleting the unicast_src ip address does not cause the VRRP instance to go to fault state
To Reproduce
Expected behavior
The VRRP instance stays in fault state if the unicast_src is not configured.
It doesn't attempt to bind to the unicast_src address until it is configured.
Keepalived version
Distro (please complete the following information):
The problem occurs regardless of distro, version or architecture
Details of any containerisation or hosted service (e.g. AWS)
None, but it wouldn't make any difference.
Configuration file:
Notify and track scripts
n/a
System Log entries
1.
Other node starts logging:
Tue Feb 11:57:53.638253974 2021: (VI_1) Received advert from 192.168.54.4 with lower priority 100, ours 101, forcing new election
and MASTER start logging
Did keepalived coredump?
No coredump
Additional context
For point 1., the following works without an error:
The text was updated successfully, but these errors were encountered: