[Debian-ha-maintainers] Bug#862248: Bug#862248: No straightforward and permanent way to disable DRBD autostart, no drbd systemd unit file

[Christian Balzer]

On Thu, 11 May 2017 09:33:59 +0300 Apollon Oikonomopoulos wrote:

> On 09:15 Thu 11 May     , Christian Balzer wrote:
> > Firstly I recreated the initial state bu unmasking drbd and enabling 
> > it, > then reloading systemd.
> > 
> > That find then gives us:
> > ---
> > /run/systemd/generator.late/drbd.service
> > /etc/systemd/system/multi-user.target.wants/drbd.service  
> 
> So, now we need ls -l 
> /etc/systemd/system/multi-user.target.wants/drbd.service to see how old 
> the symlink is and where it points to. Can you also zgrep drbd-utils 
> /var/log/dpkg.log*?
> 


Sure thing, that's quite the old chestnut indeed:
---
lrwxrwxrwx 1 root root 32 Aug 11  2015 /etc/systemd/system/multi-user.target.wants/drbd.service -> /lib/systemd/system/drbd.service
---

Note that this link is also present on:
A Wheezy system with "8.9.2~rc1-1~bpo70+1" installed.
On a system that was initially installed with Jessie but had
8.9.2~rc1-2+deb8u1 installed first.
The plot thickens, see below.

No trace of the original install, just the upgrades when going from Wheezy
to Jessie:
---
/var/log/dpkg.log:2017-05-09 13:03:35 upgrade drbd-utils:amd64 8.9.2~rc1-1~bpo70+1 8.9.2~rc1-2+deb8u1
/var/log/dpkg.log:2017-05-09 13:14:41 upgrade drbd-utils:amd64 8.9.2~rc1-2+deb8u1 8.9.5-1~bpo8+1
---

As for Ferenc, that was of course _after_ again disabling drbd, but I
wanted to start from the same state as before, so I unmasked and
enabled it first.

Also for the record, on another Jessie system that never had drbd-utils
installed I installed directly "8.9.5-1~bpo8+1". There disable works as
expected and only leaves the /run/systemd/generator.late/drbd.service
around.

So all points to 8.9.2~rc1 as the culprit.

Christian
-- 
Christian Balzer        Network/Systems Engineer                
chibi at gol.com   	Global OnLine Japan/Rakuten Communications
http://www.gol.com/