[Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

[Sam Hartman]

>>>>> "Guido" == Guido Günther <agx at sigxcpu.org> writes:

    Guido> Hi,
    Guido> On Mon, Apr 15, 2019 at 02:38:27PM -0400, Sam Hartman wrote:
    >> control: severity -1 serious
    >> 
    >> justification: libvirtd upgrades from stretch to buster break
    >> causing apt to fail and requiring the admin to get the systemd
    >> units into a consistent state before things can continue
    >> 
    >> 
    >> Unfortunately based on discussion so far this is a complex bug to
    >> fix.  Ubuntu's solution is to drop the sysv scripts and to drop
    >> Also= lines in some of the units.

    Guido> Did you reproduce this bug on a stretch->buster upgrade?
    Guido> Cause I just did that and didn't encounter any errors.

I've run into this on two active server upgrades--servers that were
running VMs,
but I haven't been able to reproduce on a clean install.
It's frustrating: on my machines where I really want the upgrade to be
smoothe this bit me, but on all my toy tests, it didn't happen.
What I think may be necessary is for virtlogd to be active.
So it may be necessary to actually get libvirtd running and actually
running a VM to use the socket before the issue comes up.
Alternatively, it's possible some other change has fixed this in the
last month.
I'll certainly say that a month ago ran into this on two different VM
servers.