** Changed in: curtin (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: curtin (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
curtin 0.1.0~bzr425-0ubuntu was installed out of xenial-updates and the
non-default MTU does indeed get into /e/n/i.
>From a deployed node's /e/n/i:
auto ens7f0
iface ens7f0 inet manual
bond-xmit_hash_policy encap3+4
bond-mode 802.3ad
bond-master bond2
mtu 9202
bond-lacp_rate f
ddstreet's ppa included a hotfix for this which was installed on Cust
lab MAAS region controller. A machine was deployed which included a
subnet defined with MTU 9202 and two NICs in a bond. After deployment,
the bond showed MTU 9202 (used ifconfig), and the /e/n/interfaces file
was coded in a wa
This is fix-committed in revno 421.
** Changed in: curtin
Status: Incomplete => Fix Committed
** Changed in: curtin
Importance: Undecided => Medium
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Confirm
