MaaS should use configured names for VLAN interfaces

Bug #1637246 reported by Stefan Bader
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Mike Pontillo
2.0
Won't Fix
Wishlist
Unassigned
maas (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Release: Xenial/16.04
MaaS version: 2.0.0+bzr5189-0ubuntu1~16.04.1

On an initial attempt to install MaaS I had a VLAN defined in /etc/network/interfaces which was called vlan10 (and defining the base device as an option). The interface was discovered but MaaS was using em0.10 as the interface name. This was mainly a problem because that also used for configuring DHCP services which of course could not find any interface of that name to bind to.

Related branches

Changed in maas:
milestone: none → next
milestone: next → none
status: New → Confirmed
importance: Undecided → Wishlist
Changed in maas:
milestone: none → 2.1.1
importance: Wishlist → High
no longer affects: maas/2.1
Changed in maas:
assignee: nobody → Mike Pontillo (mpontillo)
status: Confirmed → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Changed in maas (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.