-
-
Notifications
You must be signed in to change notification settings - Fork 737
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 when updating VMAC with a non-existent VMAC base interface #2280
Comments
A more complicated scenario works with the patches
|
louis-6wind
changed the title
VRRPv3 IPv6: persistent FAULT state when setting inexistent VMAC base interface
VRRPv3 IPv6: persistent FAULT state when setting non-existent VMAC base interface
Apr 4, 2023
louis-6wind
changed the title
VRRPv3 IPv6: persistent FAULT state when setting non-existent VMAC base interface
VRRPv3 IPv6: persistent FAULT state when updating VMAC with a non-existent VMAC base interface
Apr 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
VRRPv3 IPv6 remains in a persistent FAULT state after setting an non-existent VMAC base interface. When the base interface appears, the problem is not solved. Base interface is never updated on the vmac.
To Reproduce
On a standalone VM machine
Expected behavior
Instance in MASTER state. VMAC updated with the correct base interface
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: