[Bug 1510345] Re: Network is unreachable Wily ec2 c4 instance family

Ben Howard ben.howard at canonical.com
Thu Oct 29 16:20:54 UTC 2015


I've made "ami-614c3c0b" (HVM instance store) public early for
validation. I've confirmed that the ixgbevf driver is properly
identified as eth0.  Its going to be few more hours as the publication
continues.

ubuntu at ip-10-0-129-209:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 15.10
Release:	15.10
Codename:	wily

ubuntu at ip-10-0-129-209:~$ cat /etc/cloud/build.info 
build_name: server
serial: 20151029

ubuntu at ip-10-0-129-209:~$ dmesg | grep ixgbe
[    1.639387] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.12.1-k
[    1.641374] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.660704] ixgbevf 0000:00:03.0: 12:57:b0:c0:b3:15
[    1.661828] ixgbevf 0000:00:03.0: MAC: 1
[    1.662849] ixgbevf 0000:00:03.0: Intel(R) 82599 Virtual Function
[   11.984847] ixgbevf 0000:00:03.0: NIC Link is Up 10 Gbps

ubuntu at ip-10-0-129-209:~$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 12:57:b0:c0:b3:15  
          inet addr:10.0.129.209  Bcast:10.0.129.255  Mask:255.255.255.0
          inet6 addr: fe80::1057:b0ff:fec0:b315/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9001  Metric:1
          RX packets:61828 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2853 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:92201765 (92.2 MB)  TX bytes:251326 (251.3 KB)

ubuntu at ip-10-0-129-209:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs net.ifnames=0


** Summary changed:

- Network is unreachable Wily ec2 c4 instance family
+ [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules

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



More information about the foundations-bugs mailing list