[Bug 1423626] [NEW] Inconsistent device naming depending on install method - biosdevname/no biosdevname

[James Page]

Public bug reported:

After some discussion and debugging in the #juju channel today, we hit
upon an issue between the different install types in MAAS;  specifically
the traditional d-i based install (default in 1.5.x) ends up with
biosdevname installed, and the fast-path install does not.

This results in the same physical hardware having different naming for
its network interfaces - em1 or eth0 depending on whether biosdevname is
installed or not.

This is all technically correct, but not consistent so trips people out
- specifically a machine with biosdevname installed ends up with a juju-
br0 which is not wired to the outside world, as juju uses the
commissioning data in MAAS, which was done without biosdevname so is
ethX not emX.

Switching to the fast installer resolves this problem, but it highlights
a problem that MAAS and Juju need to deal with.

** Affects: juju-core
     Importance: Undecided
         Status: New

** Affects: maas
     Importance: Undecided
         Status: New

** Affects: maas (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: maas
   Importance: Undecided
       Status: New

** Also affects: juju-core
   Importance: Undecided
       Status: New

** Summary changed:

- Inconsistent device naming depending on install method
+ Inconsistent device naming depending on install method - biosdevname/no biosdevname

-- 
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