[Pkg-puppet-devel] Bug#1050343: puppetserver: confusing state of systemd units after upgrading from puppet-master

[Cyril Brulebois]

Package: puppetserver
Version: 7.9.5-2
Severity: important

Hi,

After a bullseye to bookworm upgrade, my system was left in a weird
state; since that's a rather old system, which went through a lot of
upgrades, I've checked that I could reproduce the following in a fresh
bullseye VM, installing puppet-master, then dist-upgrading to bookworm:
that's indeed the case.

Initially (on bullseye), we have a proper puppet-master systemd unit.
After the upgrade, there's still one, but that's using the LSB
generator, possibly because puppet-master is still installed, and its
(unchanged) /etc/init.d/puppet-master script is picked up by systemd and
its systemd-sysv-generator.

That unit of course fails as it tries to run `puppet master` and that
subcommand is gone.

Workaround:

    systemctl disable --now puppet-master
    systemctl reset-failed puppet-master


Meanwhile, a puppetserver.service unit has been deployed, with
`systemctl status` reporting it disabled even though the preset is
enabled.

Workaround:

    systemctl enable --now puppetservice

I was really surprised by the startup time, until I discovered the
server is now Java-based, hence 30 seconds to start. The increase in
memory footprint is also very noticeable. I might follow up here with
a configuration tweak in case it's useful to other users migrating
from the good old built-in server that nobody was supposed to run but
that worked so well for a number of use cases…


Cheers,
-- 
Cyril Brulebois (kibi at debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant