** Description changed: + Tested with ami-305d115a and equivalent nightly builds from 2015-12-08 + and 2015-12-10. It's possible to work around the issue by copying the + image's snapshot and changing eth0 to ens3 in + /etc/network/interfaces.d/eth0.cfg prior to first boot, but most users + probably won't think to do that since it's not actually possible to get + access to the file system over SSH before applying the workaround. + Copied from https://bugs.launchpad.net/ubuntu/+source/livecd- rootfs/+bug/1510345: 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
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525015 Title: Regression of #1510345: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1525015/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
