[Debian-ha-maintainers] Bug#993575: heartbeat: Heartbeat not starting due to missing directory after bullseye upgrade

[Gael Le Mignot]

Package: heartbeat
Version: 1:3.0.6-11
Severity: normal

Dear Maintainer,

After upgrading from buster to bullseye on several hosts, "heartbeat"
doesn't start. It tries to create a /run/heartbeat/register socket in
a non-existing /run/heartbeat/ directory.

Doing a "systemctl edit heartbeat.service" and adding :

[Service]
RuntimeDirectory=heartbeat
RuntimeDirectoryMode=755

fixes the issue.

But shouldn't a standard buster => bullseye upgrade work smoothly
without having to do such kind of workaround ?

I didn't try a fresh install of heartbeat on bullseye yet, not sure
what's the behavior then.

Regards,

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages heartbeat depends on:
ii  adduser              3.118
ii  cluster-glue         1.0.12-20
ii  gawk                 1:5.1.0-1
ii  iproute2             5.10.0-4
ii  iputils-ping [ping]  3:20210202-1
ii  libc6                2.31-13
ii  libglib2.0-0         2.66.8-1
ii  libheartbeat2        1:3.0.6-11
ii  libpam-runtime       1.4.0-9
ii  libpils2             1.0.12-20
ii  libplumb2            1.0.12-20
ii  libplumbgpl2         1.0.12-20
ii  libstonith1          1.0.12-20
ii  libxml2-utils        2.9.10+dfsg-6.7
ii  psmisc               23.4-2
ii  python3              3.9.2-3
ii  resource-agents      1:4.7.0-1

Versions of packages heartbeat recommends:
ii  iptables                     1.8.7-1
ii  logrotate                    3.18.0-2
pn  pacemaker                    <none>
ii  rsyslog [system-log-daemon]  8.2102.0-2

heartbeat suggests no packages.

-- no debconf information