I see the names are consistent across MAAS UI and deployment. However,
during the commissioning stage, I guess the biosdevname is not
installed, so the names on MAAS are all ethX, so after the system are
provisioned, the names in the OS are all ethX. I would rather see emX
and pXpX instead.
I run
** Changed in: maas
Status: Fix Committed => Fix Released
--
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 -
Curtin now write the udev rules in MAAS 1.9 using the name of the
interface set by commissioning or set by the user. The names will be
consistent across deployments.
D-I is not longer support is not something that should be used any more.
** Changed in: maas
Status: Triaged => Fix Committe
I'm also affected by this bug. The name of NIC keeps changing until
biosdevname is installed, and remove the /etc/udev/rules.d/70
-persistent-net.rules.
This bug makes install hard especially on network naming. and have to
tweak curtin with late_command which is very inconvenient.
--
You receive
** Tags removed: network
** Tags added: networking
--
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/
** Changed in: maas
Status: New => Triaged
--
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/n
** Changed in: maas
Importance: Undecided => Wishlist
** Changed in: maas
Milestone: None => 1.9.0
--
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 de
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 conne
With the new networking work in MAAS the idea was to create udev rules
for all interfaces so the naming is always the same from commissioning
to deployment.
I believe this would also fix this issue. Is my assumption correct?
--
You received this bug notification because you are a member of Ubunt
Please also bear in mind that biosdevname, even if installed, can be
disabled by a kernel command line argument (i.e. please don't hardcode
either an assumption of biosdevname naming based on package presence, or
any sort of hard dependency on biosdevname naming).
--
You received this bug notific
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
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
The problem in such cases is juju has little control on how the
machine's hardware (as seed by lshw) changes between commissioning and
deployment, and frankly neither has maas.
jamespage suggested that juju could "inject" a script very early (e.g. a
bootcmd) in the cloud-init userdata to try and d
12 matches
Mail list logo