-
**Describe the bug**
1) keepalived becomes master even though the operating system receives vrrp3 messages and the firewall is off
2) The sending keepalived seems to have wrong checksums in the vrrp…
-
hey @nuest and @kyleniemeyer - I started reviewing your manuscript, but I keep hitting spelling mistakes, and weird sentences - could you please find someone to proofread the draft that can help here…
vsoch updated
5 years ago
-
## Version of Singularity:
3.3.0
### Expected behavior
Just installed singularity locally on Ubuntu 18.04 LTS on windows. Able to build containers from docker fine
Cloned the github repo and …
-
**Describe the bug**
Please refer to the logs below.
**To Reproduce**
Run two keepalived instances on two VMs and reload the one with higher priority. I have reloaded five times (The configuratio…
-
**Describe the bug**
In ESXi 6.7, I set up two VMs with keepalived (see below the configuration).
As this case is using the same priority, keepalived should follow the VRRP protocol and assign the …
-
**Describe the issue**
Can we have a dbus signal for SIGUSR1 and SIGUSR2.This is a feature request and not an issue.
This would help applications not to send continuous signals when another signal …
-
**Describe the bug**
Running Debian 10, Buster, keepalived starts perfectly and applied the configuration to the IPVS subsystem. However it seems that the process is not able to manipulate this in an…
-
**Describe the bug**
The attempt to create ipvlan interface is successfully finish with warning:
`
Keepalived_vrrp[1998]: (VI_EXT_MP13): Success creating ipvlan interface vrrp10
Keepalived_vrrp[…
-
Are you considering adding a deployment guide, perhaps using a container of some kind?
-
**Describe the bug**
track file feature - when the priority is decreased and then further decreased to FAULT condition (with -254), the previous priority value is saved. When the track file returns s…