Closed ospalax closed 3 years ago
Also:
localhost:~# keepalived -t
Sync group vrouter has only 1 virtual router(s) - this probably isn't what you want
localhost:~# echo $?
4
No, it is what I want...
Please return everything as it was in earlier versions of the product. We really need this in our use cases.
@skydevil56 You request Please return everything as it was in earlier versions of the product
. Can you be clear about how you want keepalived to work - there have been earlier versions where a sync group was allowed to have only one VRRP instance, and also versions where a sync group was NOT allowed to have only one VRRP instance.
Commit ca175a5 now allows sync groups with only one VRRP instance again.
It was indeed commit 21cb73d that stopped sync groups with only one VRRP instance, although it looks as though that wasn't an intended change of the commit.
@pqarmitage Thank you! I already did workaround this issue in my setup but it definitively uglyfied my scripts... Once the change gets into Alpine I will happily drop the workaround. Thanks again for the prompt solution!
@skydevil56 You request
Please return everything as it was in earlier versions of the product
. Can you be clear about how you want keepalived to work - there have been earlier versions where a sync group was allowed to have only one VRRP instance, and also versions where a sync group was NOT allowed to have only one VRRP instance.
We need to be allowed to have one VRRP instance in sync groups.
@pqarmitage I checked out the commit https://github.com/acassen/keepalived/commit/ca175a582e877e669f3527a2549e1f5fc586dc78 and I have rebuild the keepalived in Alpine and I verified that the commit fixes the issue - I am closing this - feel free to reopen for whatever reason. Thanks!
Describe the bug Notify scripts (defined in group) are not executed if there is only one instance in the group. This worked fine in 2.0.19 version.
Basically the issue was already encountered here: https://github.com/acassen/keepalived/issues/594
And it was (IMHO) reintroduced in this commit: https://github.com/acassen/keepalived/commit/21cb73d00d61f296b31ec1a58e17bba4c66f4d71
To Reproduce Any steps necessary to reproduce the behaviour:
Just use config similar to this and start keepalived (
2.2.0
for example) - notify script will not be run:This will be written in the console/log:
Expected behavior PLEASE, accept once and for all a group with just one interface and don't flip-flop between the behavior... It has its uses... In my scenario it is a dynamic configuration and ad hoc adding and removing interfaces...
Keepalived version
Distro (please complete the following information):
Details of any containerisation or hosted service (e.g. AWS) Running as QEMU/KVM VM in OpenNebula.
Configuration file:
Notify and track scripts
System Log entries
Additional context The requested behavior worked in Alpine
3.11
and keepalived2.0.19
- it was broken with upgrade to Alpine3.13
and keepalived version of2.2.0
.