touch-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Oh right and the trace command that Steve used will show a call to init
early on which passes in a state fd which then, a bit later, seems to be
used as command stream to a shell. A construct like that was the parent
of mounted-tmp runs I observed. So I assume this is the method to
execute upstart scripts... but anyway.

And oh #2 @Steve: to make things even more fun it seems that the "does
not reproduce" is not depending on the use of --write-state-file but on
the fact that you have to interrupt the boot and then directly boot into
the live mode instead of making that selection graphically...Even more
fun it seems... Oddly it seems that in those cases the execve for init
seems to use a different fd number than later calls of sh use for input.
But again might be just fluke...

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

Title:
  installing or upgrading libc6 in Trusty removes all content from /tmp
  directory

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  We are seeing an issue with installation of dkms package during a
  curtin installation which ends up with /tmp directory being wiped
  clean. This is very bad for curtin as it saves critical installation
  files in /tmp.

  It turns out that it's the of upgrading libc6, which is triggered as a
  result of installing dependencies, that removes content of /tmp. For
  example, installation of gcc results in the same result since it ends
  up with libc6 being upgraded. The only way that this won't be
  recreated is if the latest libc6 is already installed.

  This problem does not exist in precise. It can also be recreated by
  installing the .deb file for any version in trusty including 2.17.

  ========================================================================
  ubuntu@host:~$ ls /tmp
  tmpHHbRkP
  ubuntu@sirrush:~$ sudo apt-get install libc6
  sudo: unable to resolve host sirrush
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    libc-dev-bin libc6-dev
  Suggested packages:
    glibc-doc
  Recommended packages:
    manpages-dev
  The following packages will be upgraded:
    libc-dev-bin libc6 libc6-dev
  3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
  Need to get 6,714 kB of archives.
  After this operation, 6,144 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB]
  Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin amd64 2.19-0ubuntu6.6 [68.9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 2.19-0ubuntu6.6 [4,735 kB]
  Fetched 6,714 kB in 0s (18.5 MB/s)
  Preconfiguring packages ...
  (Reading database ... 57798 files and directories currently installed.)
  Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ...
  Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Setting up libc6:amd64 (2.19-0ubuntu6.6) ...
  Setting up libc-dev-bin (2.19-0ubuntu6.6) ...
  Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  ubuntu@host:~$ ls /tmp
  ubuntu@host:~$
  ========================================================================

  This is very recreatable.

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