I agree that the workaround isn't sufficient and this should really work out of the box, so I've added this to the server team's backlog. But since it is reported fixed in Bionic and a workaround is available for Xenial, I'm prioritising other work over this bug. If someone can figure out and provide a patch, we'll help you get it landed. Otherwise, I expect this bug to remain inactive for a while, but hopefully we can get to it the next time someone from the server team tries to clear out some of the bugs open against keepalived.
-- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1800159 Title: keepalived does not autoload the ip_vs kernel module when it is required Status in keepalived package in Ubuntu: Triaged Status in keepalived package in Debian: New Bug description: 1) Description: Ubuntu 16.04.5 LTS Release: 16.04 2) keepalived: Installed: 1:1.2.24-1ubuntu0.16.04.1 Candidate: 1:1.2.24-1ubuntu0.16.04.1 Version table: *** 1:1.2.24-1ubuntu0.16.04.1 500 500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3) not loading the kernel module systemctl start keepalived.service Keepalived_healthcheckers[1680]: IPVS: Protocol not available Keepalived_healthcheckers[1680]: message repeated 8 times: [ IPVS: Protocol not available] ... 4) loading the module manually systemctl stop keepalived.service modprobe ip_vs kernel: [ 445.363609] IPVS: ipvs loaded. systemctl start keepalived.service Keepalived_healthcheckers[5533]: Initializing ipvs kernel: [ 600.828683] IPVS: [wlc] scheduler registered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1800159/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
