Blake, yes that's correct - having stable names based on udev rules, especially discoverable via the API will be the proper way to fix this for MAAS. The solution proposed in comment #1 could potentially work for any provider, but relying on networking features (discovery, configuration, even connectivity) during boot is racy and unreliable with current cloud-init support (2.0 will hopefully solve this).
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1423626 Title: Inconsistent device naming depending on install method - biosdevname/no biosdevname To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1423626/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
