[Bug 1510345] Update Released

[Steve Langasek]

The verification of the Stable Release Update for livecd-rootfs has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1510345

Title:
  [SRU] Cloud Images do not bring up networking w/ certain virtual NICs
  due to device naming rules

Status in Ubuntu on EC2:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Wily:
  Fix Released
Status in cloud-init source package in Xenial:
  Triaged
Status in livecd-rootfs source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  [IMPACT] Cloud images produced by livecd-rootfs are not accessable
  when presented with certain NICS such as ixgbevf used on HVM instances
  for AWS.

  [CAUSE] Changes in default device naming in 15.10 causes some devices
  to be named at boot time and are not predicatable, i.e. instead of
  "eth0" being the first NIC, "ens3" might be used.

  [FIX] Boot instances with "net.ifnames=0". This change reverts to the
  old device naming conventions. As a fix, this is the most appropriate
  since the cloud images configure the first NIC for DHCP.

  [TEST CASE1]:
  - Build image from -proposed
  - Boot image in KVM, i.e:
    $ qemu-system-x86_64 \
     -smp 2 -m 1024 -machine accel=kvm \
     -drive file=build.img,if=virtio,bus=0,cache=unsafe,unit=0,snapshot=on \
     -net nic,model=rtl8139
  - Confirm that image has "eth0"

  [TEST CASE2]:
  - Build image from -proposed
  - Publish image to AWS as HVM w/ SRIOV enabled
  - Confirm that instance boots and is accessable via SSH

  [ORIGINAL REPORT]

  I've made several attempts to launch a c4.xlarge and c4.8xlarge
  instances using Ubuntu 15.10 Wily but am unable to ping the instance
  after it has started running. The console shows that the instance
  reachability check failed.

  I am able to successfully launch c4.xlarge instances using Ubuntu
  14.04 and t2.large instances using Ubuntu 15.10.

  I've tried with both of these instance AMIs:

  ubuntu/images/hvm-ssd/ubuntu-wily-15.10-amd64-server-20151021 - ami-225ebd11
  ubuntu/images-testing/hvm-ssd/ubuntu-wily-daily-amd64-server-20151026 - ami-ea20cdd9

  Might there be a problem with the Ubuntu Kernel in 15.10 for the c4
  instances?

  Looking at the system log it seems that the network never comes up:

  [  140.699509] cloud-init[1469]: 2015-10-26 20:45:49,887 -
  url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04
  /meta-data/instance-id' failed [0/120s]: request error [('Connection
  aborted.', OSError(101, 'Network is unreachable'))]

  Thread at AWS forums:
  https://forums.aws.amazon.com/thread.jspa?threadID=218656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-on-ec2/+bug/1510345/+subscriptions