[Bug 1061639] Re: Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects

[Russell Faull]

Me too!

On several installations, with or without network-manager (wicd
instead). I have tried workarounds suggested by yota (#16 and #21) and
ernie 07 (#20) without success.

Different filesystems are all affected, with JFS seeming to recover the
fastest (but JFS is not yet suitable for SSDs with kernel 3.5.0.*). I
have lost data with XFS and needed to recover with an image of the
partition. My main laptop with ext4 has always recovered on reboot but
needs to replay the journal each time. (I use fsarchiver regularly to
backup.)

Like others, I did not see this happen on 12.04, i.e. before upstart.

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

Title:
  Upstartification of /etc/init.d/networking has lost deconfiguring-
  networking event causing bad side-effects

Status in “ifupdown” package in Ubuntu:
  Fix Released
Status in “ifupdown” source package in Quantal:
  Fix Released

Bug description:
  In precise, /etc/init.d/networking was a true SysV service script that
  did the following:

  initctl emit deconfiguring-networking

  In quantal, /etc/init.d/networking is now using the upstart-job
  symlink back to the upstart job /etc/init/networking.conf.

  The problem is that the 'deconfiguring-networking' is no longer being
  emitted. This causes dbus to fail to stop on system shutdown which
  causes a cascading effect whereby other Upstart jobs are also not shut
  down. Eventually, the system halt with the message:

  mount: / is busy

  This results in a unclean shutdown which can result in FSCK being run
  / slow / bad user boot experience.

  The two main options here are:

  1) Re-instate the 'deconfiguring-networking' event.
  2) Change the dbus 'stop on' condition and update upstart-events.7 to remove 'deconfiguring-networking'.

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