I'm setting `won't fix` for 3.4 and 3.5 as the fix involves a DB patch
and we generally want to avoid backporting such fixes unless it's really
crucial.
If it's crucial to have this fixed in 3.4 and 3.5 let me know.
** Changed in: maas/3.4
Status: In Progress => Won't Fix
** Changed in: maas/3.5
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2027975
Title:
Add check on network interface name's length
Status in cloud-init:
Fix Released
Status in MAAS:
Fix Committed
Status in MAAS 3.4 series:
Won't Fix
Status in MAAS 3.5 series:
Won't Fix
Bug description:
When adding a VLAN on long network interfaces, Cloud-init will fail
silently to add the sub-interfaces.
Deployed environment is :
* MAAS 3.3.4
* Server Dell R630 + Mellanox Connectx-5
* name of interfaces : enp130s0f0np0 / enp130s0f1np1
* add a VLAN like 100-4093
Cloud-Init will not display any error message but the VLAN interfaces will
not be added after the deployment.
If trying to perform the operation manually, we are then greeted with the
following error message.
```
ubuntu@R630:~$ sudo ip link add link enp130s0f0np0 name enp130s0f0np0.103
type vlan id 103
Error: argument "enp130s0f0np0.103" is wrong: "name" not a valid ifname
```
From Iproute2 and Kernel perspective, it is not possible to have
interfaces with a name longer than 15 characters in total.
A quick workaround is simply to rename the network interface to something
shorter.
Having a quick warning from MAAS would be nice to have to understand the
origin of the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2027975/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
