yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This is belived fixed in 0.7.8 per my last comment.


** Changed in: cloud-init
       Status: Fix Committed => Fix Released

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

Title:
  providing network-interfaces via meta-data broken in NoCloud

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  Originally reported after bug 1577982 was fixed, there is an issue
  providing network configuration to the NoCloud datasource via the
  meta-data key 'network-interfaces'.

  For example:
  $ cd /var/lib/cloud/seed/nocloud-net
  $ cat meta-data
  instance-id: 1470899540
  local-hostname: soscared
  network-interfaces: |
      auto eth0
      iface eth0 inet static
      hwaddr 00:16:3e:70:e1:04
      address 103.225.10.12
      netmask 255.255.255.0
      gateway 103.225.10.1
      dns-servers 8.8.8.8

  
  It should be noted that without providing 'hwaddr' above, you'll be relying on kernel network or systemd network device naming to have the device named 'eth0'.  If it is not named 'eth0', then configuration wont work.

  So the two options to do that right are:
   a.) provide 'hwaddr' as shown above
   b.) provide 'net.ifnames=0' on kernel command line (https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/).

  (Note, when run in lxc, you will get eth0 names consistently and you
  do not need the hwaddr or kernel command line).

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