← Back to team overview

touch-packages team mailing list archive

[Bug 1455828] Re: machinctl/systemd-nspawn containers/processes end in wrong slice

 

This bug was fixed in the package systemd - 228-1ubuntu2

---------------
systemd (228-1ubuntu2) xenial; urgency=medium

  * Merge with Debian to fix FTBFS.

systemd (228-3) UNRELEASED; urgency=medium

  * debian/rules: Remove temporary debug output from test failures again. All
    Debian buildd kernels are recent enough now, but add a check for kernels
    older than 3.13 and ignore test failures for those.

systemd (228-2) unstable; urgency=medium

  * Remove wrong endianess conversion in test-siphash24 to fix FTBFS on
    big-endian machines.
  * Bump libseccomp-dev build dependency to indicate required versions for
    backporting to jessie. (Closes: #805497)

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Thu, 19 Nov 2015 12:41:25
+0100

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1455828

Title:
  machinctl/systemd-nspawn containers/processes end in wrong slice

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Starting a Container via systemd-nspawn it is supposed to run in the machine.slice.
  While on Fedora 21 (systemd 216) it works like expected. 

  In Unbuntu 15.04 (systemd 219)

  Slice=system-systemd\x5cx2dnspawn.slice
  ControlGroup=/system.slice/system-systemd\x5cx2dnspawn.slice/systemd-nspawn@jessie02.service

  On Fedora 21:
  Slice=machine.slice
  ControlGroup=/machine.slice/machine-jessie.scope

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


References