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

[Colin Watson]

Hello Laurence, or anyone else affected,

Accepted livecd-rootfs into wily-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.349.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: livecd-rootfs (Ubuntu Wily)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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 livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Wily:
  Fix Committed
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