booting with multiple nics broken due to ip=::::hostname
Bug #1052660 reported by
Scott Moser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
my changes for kernel cmdline cleanup changed:
ip=dhcp
to
ip=::::<hostname>
caused issue if there were multiple network interfaces. The new format tries to bring up all avialable interfaces.
The short fix here is to just do:
ip=:::
However, then we're hard-coding the device name, and nothing is going to cause BOOTIF to be eth0. AFAIK, there is no way to do effectively:
ip=:::
http://
Related branches
lp:~smoser/maas/lp1052660
- Andres Rodriguez (community): Approve
-
Diff: 25 lines (+2/-2)2 files modifiedsrc/provisioningserver/kernel_opts.py (+1/-1)
src/provisioningserver/tests/test_kernel_opts.py (+1/-1)
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
| Changed in maas: | |
| status: | New → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm reverting to:
ip=dhcp
because that ends up doing:
ipconfig -t ${ROUNDTTT} -c ${IP} -d "${DEVICE}"
where DEVICE the device that maps to BOOTIF.
We had moved to 'ip=:::<hostname>' because ipconfig in the kernel then uses 'hostname' in its dhcp request. The end result being that maas can send such a thing on the cmdline, and then ddns would magically know about the system (bug 1046405).