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

** Also affects: upstart (Ubuntu Oneiric)
   Importance: Undecided
       Status: New

** Changed in: upstart (Ubuntu Oneiric)
       Status: New => Invalid

** Changed in: sysvinit (Ubuntu Oneiric)
       Status: New => In Progress

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

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

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

** Description changed:

+ == SRU JUSTIFICATION ==
+ 
+ IMPACT: its possible, though not all that likely, that files and
+ metadata will be out of sync when systems are shutdown or rebooted after
+ upgrading upstart or any of the libraries it depends on (namely, libc6).
+ Therefore the potential impact is data corruption.
+ 
+ TEST CASE:
+ 
  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 
+ mount: / is busy
+ This error will not show when the bug is fixed.
+ 
+ DEV FIX: The problem is that /var/run is cleared out for the transition
+ to /run before the 'init.upgraded' flag file is checked for. The order
+ of operations is changed.
+ 
+ REGRESSION POTENTIAL: The code path that is changed is very straight
+ forward and tight, just swapping the order of two basic sets of
+ operations. I would consider this to have a low regression potential
+ then.
+ 
+ =====
  
  This causes filesystem recovery errors on next boot.
  
  The post-upgrade lsof is attached.

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

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

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to