[Bug 1149527] Re: upstart kills ipv6 networking

[Steve Langasek]

> But as soon as I run "exec /sbin/init" from that bash prompt the machine
> once again starts ignoring ipv6, so clearly something that upstart is
> doing is killing the ipv6. 

Well, the "something that upstart is doing" is "booting the system and
running the configured scripts and jobs".  Upstart itself doesn't touch
the network stack at all.  So even though you say ifupdown isn't
configured to manage any of the network interfaces, I'm reassigning the
bug there for further analysis.

** Package changed: upstart (Ubuntu) => ifupdown (Ubuntu)

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

Title:
  upstart kills ipv6 networking

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  I have a machine here that network boots (i.e. no resident hard disk,
  pxeboot and nfsroot) and during it's boot it gets an ipv6 address on
  our network but after it's booted, even though it still has an ipv6
  network configured (address and routing) any ipv6 packets sent to it
  are ignored and the machine cannot send any out.

  Now, what's strange about this is if I boot this machine with
  "init=/bin/bash" when that bash process is started as init (i.e. with
  PID==1) ipv6 networking works fine.  I can ping6 the machine from
  other machines in the network, etc.

  But as soon as I run "exec /sbin/init" from that bash prompt the
  machine once again starts ignoring ipv6, so clearly something that
  upstart is doing is killing the ipv6.  The question is however, to
  discover what that is.  I know about upstart's "--verbose" but
  ultimately that is too verbose and the results scroll off of the
  screen (and out of the tty's buffer) before I can see what upstart is
  doing.  And unfortunately this machine has no serial port which I can
  make a console to log elsewhere.

  What would be really nice is an option to upstart to stop and display
  the name of each job that is going to be run with a "hit return" type
  confirmation to actually run it.  Then I could confirm each script and
  see which one is killing the ipv6 networking.

  To be thorough, I want to confirm there are no interfaces other than
  lo defined in /etc/network/interfaces and network-manager is not
  installed and/or enabled on this machine.  As much as I would like to
  be able to use either of those they both have the problem that they
  turn an interface down before bringing it "up" and that kills NFS (of
  course) which kills the root filesystem which hangs the node.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upstart 1.5-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  Date: Wed Mar  6 08:23:29 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)

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