[Keepalived-devel] Issue with priority when issuing SIGHUP

[Paul G. <gi...@tc...>]

Hello,

I noticed an issue with changing my VRRP config and issuing a SIGHUP
instead of stopping and restarting the keepalived process, after each
config change I issue a SIGHUP to update values. Usually this works fine
but not in the case of changing priorities and decrementing using a tracked
interface.

Originally I had a priority of 50 with a tracked interface having a
decrement value of -7. I bought down the tracked interface and then I
proceeded to change the priority to 110 and the decrement value to -11. The
log then indicates that the effective priority changed correctly from 100
to 99, everything seems to be fine with the new values selected.

I then brought back up the tracked interface and at this stage there is
some internal inconsistency because the message in the log states "Changing
effective priority from 103 to 114", remembering the old -7 decrement value
but the new priority value, and then adds the new decrement -11 value to
103 instead of 99. If I bring the tracked interface down again the value
changes from 114 to 103.

In general is this method not supported or is this a bug? Should I be
stopping/starting keepalived each time I change my config?

Separate but maybe related, I have also noticed an issue sometimes that
when I start VRRP with an interface as backup and a priority of 110, with a
decrement set of -11, when it becomes master it actually adds the decrement
to the priority and goes to 121, I need to look into that issue further
though.


Regards,

--
Paul