Ubuntu boostrap uses wrong network interface to retrive the root filesystem image
Bug #1482049 reported by
Aleksandr Shaposhnikov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Alexei Sheplyakov |
Bug Description
The live-boot initramfs picks the first connected interface and
tries to configure it via DHCP and obtain the root filesystem image.
Depending on hardware and initialization order a wrong interface can
be chosen so the boot fails.
Another issue is that the initramfs drops into a shell on error.
Custom build:
http://
summary: |
- Ubuntu bootstrap not working on some nics/networks + Ubuntu boostrap uses wrong network interface to retrive the root + filesystem image |
description: | updated |
Changed in mos: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 7.0 |
assignee: | nobody → Alexei Sheplyakov (asheplyakov) |
Changed in mos: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Apparently the version 3.0.1-1 of live-boot package shipped with Ubuntu 14.04 does not wait properly for network device initialization.
Also it does not use BOOTIF argument as passed by extlinux to figure out which interface should be used in the boot process.