> we should be careful to ignore NICs with randomly generated MACs (see bug 1936972).
ugh nics with LAA? yeah, it can be hard to 'uniquely' identify a nic, especially since it's so common to clone macs for bonds, bridges, vlans, and in some cases even duplicate hw devices with the same nic (e.g. bug 1843381). > My initial thought is that perhaps subiquity installs should do what MAAS installs do and configure netplan to always use the install-time names. I'm generally not a fan of how MAAS configures netplan to force-rename interfaces; that sounds to me like it's destined for interface naming collisions. But I don't have any better immediate suggestion for 'foolproof' matching of all possible nics that might exist across all kernel driver versions, either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1940860/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
