[Bug 1393474] Re: su call in postinst fails with "Killed" when not running from a logind shell

[Launchpad Bug Tracker]

This bug was fixed in the package autopkgtest - 3.8.1

---------------
autopkgtest (3.8.1) unstable; urgency=medium


  * If the testbed does not have root privileges (e. g. missing sudo
    password), install click packages with pkcon and skip the AppArmor rule
    adjustment. This makes non-root click tests at least work for
    non-Autopilot cases. (LP: #1384417)
  * Make --shell-fail also apply to test dependency installation failure.
  * Run root tests through "su" as well (if possible), to ensure that these
    also get a proper PAM/logind session with all runners. (LP: #1393474)
  * Skip the test_tmp_install tests if apt-get download does not work. This
    might happen in some build environments which completely disable
    networking or don't have working apt-get download for some reason.
    (Closes: #769687)
  * Don't put the log FIFO into the output directory. This avoids keeping it
    in --output-dir, which fails if the output dir happens to be in the tested
    tree itself. (LP: #1393426)
  * adt-setup-vm: Don't purge man-db. It uninstalls way too much on images
    which aren't just minimal environments.
  * adt-setup-vm: Drop bogus "X-Start-Before" line in generated init.d script.
    (Closes: #770517)
  * Respect DEB_BUILD_OPTIONS=nocheck (side issue in #769687)

 -- Martin Pitt <mpitt at debian.org>  Thu, 27 Nov 2014 10:54:02 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest 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 Released

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