[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Andy Whitcroft]

Hello RussianNeuroMancer, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu8
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Fedora:
  Unknown

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
      callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 1873, in do_install
      guest.start_install(meter=meter)
    File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
      noboot)
    File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
      dom = self.conn.createLinux(start_xml or final_xml, 0)
    File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in createLinux
      if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in syslog when this error appear on the screen (or virsh output). Both systems was upgraded from 15.10.
  ---
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2015-02-27T11:49:59.773560

  SRU INFORMATION
  ===============
  Fix: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=5c4291769cb426a

  Regression potential: This changes a central place of systemd
  (although the fix is quite obvious), so if that code is broken it
  could potentially lead to boot failure. However, the fix has been
  tested in yakkety, and all the time in upstrean and downstream CI, so
  if this would actually break anything it should have surfaced by now.
  So low overall.

  Test case: Should be verified by the reporter as the bug description
  did not include a reproducer.

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