Am 21.12.2016 um 15:19 schrieb Christoph Berg: > Re: Patrick Matthäi 2016-12-21 > <89f2fc7d-a3a0-a01f-8105-7f795b0d2...@debian.org> >> We tried out many test cases, workarounds, debugging on this issue and >> the result was, that the v1 mode of heartbeat can not deal with the >> dependency system of systemd and will never support it. > Hmm, I don't get what the dependency system has to do with it, versus > a plain "heartbeat invoking systemctl via init scripts" breakage, or > something like that. > >> I still think, this is the best solution (since only v1 mode is affected): >> "IMO the package should warn (debconf dialog prio high?) the user if he >> upgrades heartbeat and systemd+v1 config is in use." > That still requires someone to understand the problem and explain it > in the warning. Just saying "it might be broken but we don't know > which bits you need to check" won't work.
Simple service/host failovers will not work. the system will mostly stay in a not working state. Dont ask me too much now, sorry just came back from vacation and now I do not have the time to re-setup and debug everything again. Maybe someone else saved the irc logs (just search for the-me in the debian-ha channel on oftc) > >> Removing the whole heartbeat package would not be a good solution, since >> it is still required? > It doesn't have any reverse dependencies anymore. At the moment it's > the only HA package not in testing, so it isn't holding back any other > package. Effectively, it is already removed now (from testing). > > Christoph -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */