touch-packages team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Public bug reported:

I came across this when debugging bug 1352255.
as implemented right now (trusty and utopic) the 'static-network-up' event is emitted when each 'auto' interface has had *an* address configured, as opposed to *all* addresses configured.

Heres why:
 ifupdown calls runparts on /etc/network/if-up.d/ after each stanza for a network inteface, rather than once after *all* stanzas are executed.

The result is that things that were waiting on 'static-network-up',
expecting that would provide them with expected networking are not
actually guaranteed anything other than the first stanza for each
interface.

(note also that this happens to cause strange behavior in bug 1352255).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ifupdown 0.7.47.2ubuntu4.1
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Thu Oct  9 12:37:10 2014
InstallationDate: Installed on 2011-12-06 (1037 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcEnviron:
 TERM=screen-bce
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ifupdown
UpgradeStatus: Upgraded to trusty on 2014-08-01 (69 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  /etc/network/if-up.d/upstart emits static-network-up to early

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  I came across this when debugging bug 1352255.
  as implemented right now (trusty and utopic) the 'static-network-up' event is emitted when each 'auto' interface has had *an* address configured, as opposed to *all* addresses configured.

  Heres why:
   ifupdown calls runparts on /etc/network/if-up.d/ after each stanza for a network inteface, rather than once after *all* stanzas are executed.

  The result is that things that were waiting on 'static-network-up',
  expecting that would provide them with expected networking are not
  actually guaranteed anything other than the first stanza for each
  interface.

  (note also that this happens to cause strange behavior in bug
  1352255).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Oct  9 12:37:10 2014
  InstallationDate: Installed on 2011-12-06 (1037 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to trusty on 2014-08-01 (69 days ago)

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