[SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Critical
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
High
|
Scott Moser | ||
Xenial |
Fix Released
|
High
|
Scott Moser | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Wily |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned |
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.
-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/
ubuntu/
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.
Thread at AWS forums: https:/
Related branches
- Colin Watson: Approve
-
Diff: 33 lines (+7/-3)2 files modifieddebian/changelog (+6/-2)
live-build/ubuntu-cpc/hooks/999-cpc-fixes.chroot (+1/-1)
Changed in ubuntu: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Ben Howard (utlemming) |
tags: | added: cloud-images |
affects: | ubuntu → ubuntu-on-ec2 |
Changed in ubuntu-on-ec2: | |
assignee: | Ben Howard (utlemming) → nobody |
importance: | Critical → Undecided |
status: | Confirmed → New |
Changed in livecd-rootfs (Ubuntu): | |
assignee: | nobody → Ben Howard (utlemming) |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in livecd-rootfs (Ubuntu Wily): | |
status: | New → In Progress |
importance: | Undecided → Medium |
tags: | added: patch |
tags: | added: rls-x-incoming |
Changed in cloud-init (Ubuntu Xenial): | |
importance: | Undecided → High |
assignee: | nobody → Scott Moser (smoser) |
affects: | ubuntu-on-ec2 → cloud-images |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1510345/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]