[Bug 1182540] Re: Daemon-suppression code in installer breaks new invoke-rc.d logic

[Launchpad Bug Tracker]

This bug was fixed in the package debian-installer-utils - 1.97ubuntu1

---------------
debian-installer-utils (1.97ubuntu1) saucy; urgency=low

  * Resynchronise with Debian.  Remaining changes:
    - user-params: Don't propagate vga=*, break=*, *-ubiquity, or
      noninteractive to installed system.
    - Use /proc/self/fd/4 rather than /dev/fd/4 in fetch-url-methods/http;
      the latter doesn't seem to exist in d-i.
    - list-devices:
      + New "mmc-partition" type for detecting partitions on MMC devices.
      + Make sure we also detect platform-omap MMCs.
      + Don't return entries for extended partitions.
    - Don't include the battery subsystem on calls to udevadm trigger.
    - log-output: Always install a no-op SIGCHLD handler, in case the
      subsidiary process starts a daemon which does not fully disconnect its
      standard file descriptors.

debian-installer-utils (1.97) unstable; urgency=low

  * chroot-setup.sh: Make the fake initctl pass through "initctl version"
    calls, used by such things as invoke-rc.d to figure out whether it's
    running under Upstart (LP: #1182540).

debian-installer-utils (1.96) unstable; urgency=low

  [ Samuel Thibault ]
  * Make iso-scan probing a lot faster on hurd-i386 by avoiding non-existing
    partitions.

  [ Updated translations ]
  * Croatian (hr.po) by Tomislav Krznar
  *
 -- Colin Watson <cjwatson at ubuntu.com>   Wed, 22 May 2013 17:10:46 +0100

** Changed in: debian-installer-utils (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  Daemon-suppression code in installer breaks new invoke-rc.d logic

Status in “debian-installer-utils” package in Ubuntu:
  Fix Released
Status in “debootstrap” package in Ubuntu:
  Fix Committed
Status in “ubiquity” package in Ubuntu:
  Fix Committed

Bug description:
  The root of the problem as pertains to lxc is that debootstrap is
  resulting in a udev being started as a child of debootstrap.  In
  particular:

  ( flock -x 200; debootstrap saucy xxx; ) 200>/tmp/zzz
  after this completes, /proc/locks will show that /tmp/zzz is still locked;  udev will be running;  and a subsequent
  ( flock -x 200 ) 200>/tmp/zzz
  will hang.

  ========

  
  The saucy smoke test for lxc test_lxc_apparmor appears to be hung with saucy installations of 20130521.

  The following tests appear to have completed successfully.
  - test: test_lxc_reboot
  - test: test_lxc_simple
  - test: test_lxc_api

  Steps to reproduce:
  1. Install a default saucy server on a vm  (either manually or preseeded default installation) with either i386 or amd64 image using KVM, libvirt
  2. Do the following to install utah inside the VM
     sudo apt-add-repository -y ppa:utah/stable
     sudo apt-get update
     sudo apt-get install utah
  3. Run the lxc tests using
       sudo utah -r  lp:ubuntu-test-cases/server/runlists/lxc.run

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lxc 0.9.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.1-0ubuntu1
  Architecture: amd64
  Date: Tue May 21 11:30:55 2013
  InstallationDate: Installed on 2013-05-21 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha amd64 (20130521)
  MarkForUpload: True
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1182540/+subscriptions