yahoo-eng-team team mailing list archive

["Jeroen T. Vermeulen" <1377005@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When I try to deploy a MAAS node on a pure IPv6 network, it seems to
install normally and reboot, but cloud-init gives off an error about
route_info failing.  Eventually the console moves on to a login prompt,
but the machine is not reachable on the network — which means I can't
log in at all.

The console shows:
«
Cloud-init v. 0.7.5 running 'init-local' at Fri, 03 Oct 2014 04:19:29 <etc>
cloud-init-nonet[15.53]: waiting 10 seconds for network device
 * Starting Mount network filesystems
 * Stopping Mount network filesystems
cloud-init-nonet[16.46]: static networking is now up
 * Starting configure network device
Cloud-init v. 0.7.5 running 'init' at Fri, 03 Oct 2014 04:19:30 <etc>
ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++
ci-info: +--------+------+-----------+-----------+-------------------+
ci-info: | Device |  Up  |  Address  |    Mask   |     Hw-Address    |
ci-info: +--------+------+-----------+-----------+-------------------+
ci-info: |   lo   | True | 127.0.0.1 | 255.0.0.0 |                   |
ci-info: |  eth0  | True |     -     |     -     | 00:12:34:56:78:90 |
ci-info: +--------+------+-----------+-----------+-------------------+
ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
»

After that it pauses for a long time, and finally moves on to a login
prompt.

Here's what was installed in the node's /etc/network/interfaces:
«
auto lo

auto eth0

iface eth0 inet6 static
        netmask 64
        address fd0d:1777:6bb6:db7::2:1
        gateway fd0d:1777:6bb6:db7::1
»

The node doesn't show up even in neighbour discovery.  If I do the same
thing but with eth0 also configured to get a dynamic IPv4 address from
DHCP, then it boots up normally and becomes reachable through both IPv4
and IPv6.

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Description changed:

  When I try to deploy a MAAS node on a pure IPv6 network, it seems to
  install normally and reboot, but cloud-init gives off an error about
  route_info failing.  Eventually the console moves on to a login prompt,
  but the machine is not reachable on the network — which means I can't
  log in at all.
  
  The console shows:
  «
  Cloud-init v. 0.7.5 running 'init-local' at Fri, 03 Oct 2014 04:19:29 <etc>
  cloud-init-nonet[15.53]: waiting 10 seconds for network device
-  * Starting Mount network filesystems
-  * Stopping Mount network filesystems
+  * Starting Mount network filesystems
+  * Stopping Mount network filesystems
  cloud-init-nonet[16.46]: static networking is now up
-  * Starting configure network device
+  * Starting configure network device
  Cloud-init v. 0.7.5 running 'init' at Fri, 03 Oct 2014 04:19:30 <etc>
  ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++
  ci-info: +--------+------+-----------+-----------+-------------------+
  ci-info: | Device |  Up  |  Address  |    Mask   |     Hw-Address    |
  ci-info: +--------+------+-----------+-----------+-------------------+
  ci-info: |   lo   | True | 127.0.0.1 | 255.0.0.0 |                   |
  ci-info: |  eth0  | True |     -     |     -     | 00:12:34:56:78:90 |
  ci-info: +--------+------+-----------+-----------+-------------------+
  ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  »
  
  After that it pauses for a long time, and finally moves on to a login
  prompt.
  
  Here's what was installed in the node's /etc/network/interfaces:
  «
  auto lo
  
  auto eth0
  
  iface eth0 inet6 static
-         netmask 64
-         address fd0d:1777:6bb6:db7::2:1
-         gateway fd0d:1777:6bb6:db7::1
+         netmask 64
+         address fd0d:1777:6bb6:db7::2:1
+         gateway fd0d:1777:6bb6:db7::1
  »
+ 
+ The node doesn't show up even in neighbour discovery.  If I do the same
+ thing but with eth0 also configured to get a dynamic IPv4 address from
+ DHCP, then it boots up normally and becomes reachable through both IPv4
+ and IPv6.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1377005

Title:
  Breaks machine without IPv4: "Route info failed"

Status in Init scripts for use on cloud images:
  New

Bug description:
  When I try to deploy a MAAS node on a pure IPv6 network, it seems to
  install normally and reboot, but cloud-init gives off an error about
  route_info failing.  Eventually the console moves on to a login
  prompt, but the machine is not reachable on the network — which means
  I can't log in at all.

  The console shows:
  «
  Cloud-init v. 0.7.5 running 'init-local' at Fri, 03 Oct 2014 04:19:29 <etc>
  cloud-init-nonet[15.53]: waiting 10 seconds for network device
   * Starting Mount network filesystems
   * Stopping Mount network filesystems
  cloud-init-nonet[16.46]: static networking is now up
   * Starting configure network device
  Cloud-init v. 0.7.5 running 'init' at Fri, 03 Oct 2014 04:19:30 <etc>
  ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++
  ci-info: +--------+------+-----------+-----------+-------------------+
  ci-info: | Device |  Up  |  Address  |    Mask   |     Hw-Address    |
  ci-info: +--------+------+-----------+-----------+-------------------+
  ci-info: |   lo   | True | 127.0.0.1 | 255.0.0.0 |                   |
  ci-info: |  eth0  | True |     -     |     -     | 00:12:34:56:78:90 |
  ci-info: +--------+------+-----------+-----------+-------------------+
  ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  »

  After that it pauses for a long time, and finally moves on to a login
  prompt.

  Here's what was installed in the node's /etc/network/interfaces:
  «
  auto lo

  auto eth0

  iface eth0 inet6 static
          netmask 64
          address fd0d:1777:6bb6:db7::2:1
          gateway fd0d:1777:6bb6:db7::1
  »

  The node doesn't show up even in neighbour discovery.  If I do the
  same thing but with eth0 also configured to get a dynamic IPv4 address
  from DHCP, then it boots up normally and becomes reachable through
  both IPv4 and IPv6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1377005/+subscriptions