netplan ifupdown-migrate fails to handle manual interfaces
Bug #1749390 reported by
Mark Shuttleworth
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| netplan |
Triaged
|
High
|
Unassigned | ||
Bug Description
Hi have a number of interfaces that look like this in ENI:
auto p2p1
iface p2p1 inet manual
bond-master bond-protea
bond-mode balance-rr
bond-miimon 100
auto p5p1
iface p5p1 inet manual
bond-master bond-protea
bond-mode balance-rr
bond-miimon 100
auto bond-protea
iface bond-protea inet static
address 192.168.254.9/30
bond-mode balance-rr
bond-miimon 100
bond-slaves p5p1 p2p1
dns-nameservers 8.8.8.8
I'm sure that manual interface control is widespread with ifupdown, so we do need to have a matching approach with netplan. Is there such an approach, which the migration script could automate? Or do we need to design and add that now, before 18.04?
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #1 |
| Changed in netplan: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| summary: |
- netplan migration fails to handle manual interfaces + netplan ifupdown-migrate fails to handle manual interfaces |
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #2 |
To post a comment you must log in.
Triaged.
Manual/static is not supported yet by 'netplan ifupdown-migrate', but we do need to improve drastically on that story for 18.04 (and that's why I had this already on backlog, and should be scheduled for the very next iteration). For now, only the very simplest "only DHCP" case is supported.
Manual definitions are generally pretty straightforward, and at least in the provided example everything should be well supported. This is just a matter of expanding on the existing code to work through the "translation".