dhclient does not work with busybox ip
Bug #1819747 reported by
Thadeu Lima de Souza Cascardo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
busybox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned | ||
cloud-initramfs-tools (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Disco |
Invalid
|
Undecided
|
Unassigned | ||
initramfs-tools (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Disco |
Invalid
|
Undecided
|
Unassigned | ||
isc-dhcp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After isc-dhcp update from 4.3.5 to 4.4.1, dhclient-script uses valid_lft option when adding an IPv4 address.
When used on the initrd generated by initramfs-tools, this will fail because busybox ip does not support this option.
This affects the use of cloud-initramfs
Changed in initramfs-tools (Ubuntu Disco): | |
status: | New → Invalid |
Changed in isc-dhcp (Ubuntu Disco): | |
status: | New → Invalid |
Changed in cloud-initramfs-tools (Ubuntu Disco): | |
status: | New → Invalid |
Changed in busybox (Ubuntu Disco): | |
status: | New → Fix Committed |
To post a comment you must log in.
There is also a problem in dhclient where it forks off the daemon and exits before writing the pidfile which needs a separate fix.