I could never reproduce it with "real" logins, so for now I suspect that
this is due to the rather unusual way of running processes in a VM
directly on a root shell on ttyS1, which circumvents any PAM/logind. I
remember that this also breaks some other tests which expect automatic
ACLs and other things that a proper PAM session provides, so I fixed
autopkgtest to provide a PAM session in all cases:
http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=5d45a5999

** Package changed: systemd-shim (Ubuntu) => autopkgtest (Ubuntu)

** Changed in: autopkgtest (Ubuntu)
       Status: New => Fix Committed

** Changed in: autopkgtest (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  su call in postinst fails with "Killed" when not running from a logind
  shell

Status in “autopkgtest” package in Ubuntu:
  Fix Committed

Bug description:
  Recent keystone autopkgtest runs (https://jenkins.qa.ubuntu.com/job
  /vivid-adt-keystone/?) fail during installation of test dependencies:

  Setting up keystone (1:2014.2-0ubuntu1) ...
  Killed
  dpkg: error processing package keystone (--configure):
   subprocess installed post-installation script returned error exit status 137
  dpkg: dependency problems prevent configuration of adt-satdep:
   adt-satdep depends on keystone; however:
    Package keystone is not configured yet.

  This only seems to happen when running them with more than one CPU,
  like this:

      adt-run keystone --- qemu /srv/vm/adt-vivid-amd64-cloud.img --cpus
  2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to