Package: heartbeat Version: 1:3.0.5+hg12629-1.2 Severity: grave Tags: upstream Justification: causes non-serious data loss
Hello, as previous reported on IRC the v1 config style does not work with systemd as init system. Failovers are broken, because of the event based systemd, instead of LSB ordering for services. I also tried out the 1:3.0.6-2 version, without any luck. Upstream also states (have not got the link now) that it is unsupported, since v1 style does not get new features. IMO the package should warn (debconf dialog prio high?) the user if he upgrades heartbeat and systemd+v1 config is in use. Why severity grave? On setting up some test VMs I noticed that it looks like the cluster is working, but on intensive testing (just some failovers or using /usr/share/heartbeat/ scripts) everything broke again and again. For productive setups this will fail in a bigger downtime and the user could not identify the real problem (missing support) from the logs, except of some coredumps and never taking over clients. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)