-
-
Notifications
You must be signed in to change notification settings - Fork 736
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
VRRPv3 IPv6: persistent FAULT state (no IPv6 address for interface) #2275
Comments
I have applied a debug patch and I get:
Debug patch:
|
This is a regression from 4c7a94a |
Fix for the issue #2277 |
I am currently investigating this. Unfortunately the patch in #2277 is not correct. The root cause of the problem is that the vrrp instance has not been added to the list of track interfaces of the VMAC interface prior to the address being added. There is a further problem that the address is not copied from the interface to the VRRP instance if the VRRP instance is in fault state. I have the basis of a patch to resolve this, but am currently checking that it doesn't have any untoward side effects. |
@pqarmitage. Thank you for your help. Could you share with me the patch you are testing so that I can help in testing? I think that the
When a fault is found, the bit is set to 1 and reset when it recovers. |
The patch at the moment is:
With regard to your suggestion:
I am happy with the idea of changing the above to flags, but a counter is still needed for script faults, since there could be multiple scripts that are in fault state. |
It seems there is also It works on my side (I did not do some extensive tests) |
There is an update to the patch above required:
|
Describe the bug
VRRPv3 IPv6 remains in a persistent FAULT state
To Reproduce
On a standalone VM machine
Expected behavior
Instance in MASTER state.
Keepalived version
Distro (please complete the following information):
Details of any containerisation or hosted service (e.g. AWS)
NA
Configuration file:
See above
Notify and track scripts
NA
System Log entries
Did keepalived coredump?
No
The text was updated successfully, but these errors were encountered: