Comment 6 for bug 1951903

 Hey Christian, don't spend anymore time on my problem! It isn't a problem since it doesn't "break" anything.
Your diligence and expertise is recognized by me and appreciated! (it explained I don't need to worry!)

Have a pleasant Holiday!
Patrick

     On Tuesday, November 23, 2021, 12:15:46 AM PST, Christian Ehrhardt  <email address hidden> wrote:

 We know that libvirtd can't be removed as it is early in the postrm and
at this time we know it will trigger:

$ delgroup libvirtd
/usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirtd' as their primary group!

But removing it afterwards when it can be removed only ends up breaking slightly different:

RET=20 Unsupported command "the" (full line was "The group `libvirtd'
does not exist.") received from confmodule.

Maybe the sysuser config of libvirtd makes debconf want to remove it,
but in the combination we have in place this fails and that makes it
fail badly. I need to track this down in more detail, but this week will
unlikely find time for it.

As a workaround for now, I found that removing/purging libvirt-daemon-
system once more passed fine so you can just re-run whatever you did to
trigger the purges and the second time it should pass.

** Changed in: libvirt (Ubuntu)
      Status: Confirmed => Triaged

** Changed in: libvirt (Ubuntu)
  Importance: Undecided => Medium

** Tags added: server-todo

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1951903

Title:
  package libvirt-daemon-system 4.0.0-1ubuntu8.19 failed to
  install/upgrade: installed libvirt-daemon-system package post-removal
  script subprocess returned error exit status 128

Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  upgraded from 16.04? to 18.04 at end of upgrade I got libvirt-daemon-system error 128.
  I didn't change anything in the /etc/livirt/nwfilter... files like the system
  now accuses me of doing! I logged in this time through Unity to get my old desktop back and that is when I got this system report.
  I was getting a system error when I logged in after the upgrade but no error # or anything;

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libvirt-daemon-system 4.0.0-1ubuntu8.19
  ProcVersionSignature: Ubuntu 4.15.0-162.170-generic 4.15.18
  Uname: Linux 4.15.0-162-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  Date: Sun Nov 21 13:46:10 2021
  ErrorMessage: installed libvirt-daemon-system package post-removal script subprocess returned error exit status 128
  InstallationDate: Installed on 2021-11-05 (18 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-162-generic root=UUID=8c89ff08-e57d-4fb0-b472-adfde83e73b5 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  SourcePackage: libvirt
  Title: package libvirt-daemon-system 4.0.0-1ubuntu8.19 failed to install/upgrade: installed libvirt-daemon-system package post-removal script subprocess returned error exit status 128
  UpgradeStatus: Upgraded to bionic on 2021-11-21 (1 days ago)
  mtime.conffile..etc.libvirt.nwfilter.allow-arp.xml: 2021-11-22T12:30:12.396265
  mtime.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: 2021-11-22T12:30:12.428264
  mtime.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: 2021-11-22T12:30:12.408265
  mtime.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: 2021-11-22T12:30:12.416264
  mtime.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: 2021-11-22T12:30:12.444263
  mtime.conffile..etc.libvirt.nwfilter.clean-traffic.xml: 2021-11-22T12:30:12.440263
  mtime.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: 2021-11-22T12:30:12.424264
  mtime.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: 2021-11-22T12:30:12.448263
  mtime.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: 2021-11-22T12:30:12.384266
  mtime.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: 2021-11-22T12:30:12.412264
  mtime.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: 2021-11-22T12:30:12.392265
  mtime.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: 2021-11-22T12:30:12.436264
  mtime.conffile..etc.libvirt.nwfilter.no-mac-spoofing.xml: 2021-11-22T12:30:12.420264
  mtime.conffile..etc.libvirt.nwfilter.no-other-l2-traffic.xml: 2021-11-22T12:30:12.400265
  mtime.conffile..etc.libvirt.nwfilter.no-other-rarp-traffic.xml: 2021-11-22T12:30:12.432264
  mtime.conffile..etc.libvirt.nwfilter.qemu-announce-self-rarp.xml: 2021-11-22T12:30:12.452263
  mtime.conffile..etc.libvirt.nwfilter.qemu-announce-self.xml: 2021-11-22T12:30:12.404265
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2021-11-22T12:30:11.592298

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1951903/+subscriptions