[Bug 886205] [NEW] Disabling network-interface break rc-sysinit compatibility script

[Marco Gaiarin]

Public bug reported:

I've upgraded an ubuntu server installation from hardy to lucid, moving indeed from sysV-init to upstart.
I use in this server a custom set of iptables script that i run from /etc/network/if-up.d/*, and after rebooting the server nothing seems to work.

After some panic, i've found the culprit: simply my script suppose that
interfaces are brought up in the exact order they are written in
/etc/network/interfaces (this is a server, clearly they have static ip
addresses...), but upstart (better: the network-interface script)
instead brought up the interface in mixed/casual order.

So, i've commented out the 'start on' and 'stop on' rows on network-
interface.conf, but now the machine boot with correct interface order
(and so, correct iptables rules) but with little or no service
available.

Again, some panic, some work and i've found that the ''sysv
compatibility scripts'' depends only on dynamic interfaces, not static
ones.

Patch attached that solve the problem. Thanks.

PS: i've tried to read the upstart documentation to understand if
there's a better way to ''serialize'' network interface brought up. So
probably my patch solve my problem in a wrong way. Please, say me if it
is the case...

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: lucid

-- 
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/886205

Title:
  Disabling network-interface break rc-sysinit compatibility script

Status in “upstart” package in Ubuntu:
  New

Bug description:
  I've upgraded an ubuntu server installation from hardy to lucid, moving indeed from sysV-init to upstart.
  I use in this server a custom set of iptables script that i run from /etc/network/if-up.d/*, and after rebooting the server nothing seems to work.

  After some panic, i've found the culprit: simply my script suppose
  that interfaces are brought up in the exact order they are written in
  /etc/network/interfaces (this is a server, clearly they have static ip
  addresses...), but upstart (better: the network-interface script)
  instead brought up the interface in mixed/casual order.

  So, i've commented out the 'start on' and 'stop on' rows on network-
  interface.conf, but now the machine boot with correct interface order
  (and so, correct iptables rules) but with little or no service
  available.

  Again, some panic, some work and i've found that the ''sysv
  compatibility scripts'' depends only on dynamic interfaces, not static
  ones.

  Patch attached that solve the problem. Thanks.

  PS: i've tried to read the upstart documentation to understand if
  there's a better way to ''serialize'' network interface brought up. So
  probably my patch solve my problem in a wrong way. Please, say me if
  it is the case...

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