[Bug 886439] Re: upgrade to upstart 1.3-0ubuntu11 causes unclean shutdown

[Clint Byrum]

The offending code is actually in sysvinit, in /etc/init.d/umountroot

It checks for /var/run/init.upgraded *AFTER* completely removing the
contents of /var/run

We simply need to do this check before the /var/run mangling.

** Also affects: sysvinit (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: sysvinit (Ubuntu)
       Status: New => Triaged

** Changed in: sysvinit (Ubuntu)
   Importance: Undecided => High

** Changed in: sysvinit (Ubuntu)
     Assignee: (unassigned) => Clint Byrum (clint-fewbar)

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

Title:
  upgrade to upstart 1.3-0ubuntu11 causes unclean shutdown

Status in “sysvinit” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1.  Start an Ubuntu 11.10 Oneiric instance on EC2.
  Example: ec2run ami-bbf539d2 -t t1.micro -k key
  2.  Save sudo lsof for reference.
  3.  apt-cache show upstart
  The stock version of upstart installed is 1.3-0ubuntu10.
  4.  sudo apt-get update; sudo apt-get install upstart
  upstart is upgraded to 1.3-0ubuntu11
  5.  Verify that /var/run/init.upgraded is in fact touched by the install.
  6.  Save sudo lsof for reference.
  7.  sudo shutdown -h now
  The console displays while unmounting:
  mount: / is busy 

  This causes filesystem recovery errors on next boot.

  The post-upgrade lsof is attached.

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