MAAS does not allow duplicate MAC between fabrics
Bug #1928391 reported by
Bart Vrancken
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MAAS | Status tracked in 3.6 | |||||
| 3.5 |
Won't Fix
|
Low
|
Unassigned | |||
| 3.6 |
Triaged
|
Low
|
Unassigned | |||
Bug Description
Use case:
A device with 1 ethernet port that is used in a Trunk (multiple VLAN's). By default the OS creates Layer2 VLAN interfaces with the same MAC address as the main interface. This is a legitimate use case for e.g. routers.
e.g.
eth1@vlan10 00:50:56:a0:85:5a 192.168.10.1
eth2@vlan20 00:50:56:a0:85:5a 192.168.20.1
Description:
I am adding this as a device, not a machine. I understand that a machine needs to be more strict. It will never boot, but i want the device to be defined to utilize DNS thoughout the network.
Problem:
Maas does not allow the usage of a duplicate MAC. However the 'lock' should be extended to look within the fabric of the subnet, ergo if you select two different fabrics it should allow the creation.
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Jerzy Husakowski (jhusakowski) wrote | #1 |
| Changed in maas: | |
| importance: | Medium → Low |
| milestone: | none → 3.5.0 |
| Changed in maas: | |
| milestone: | 3.5.0 → 3.5.x |
To post a comment you must log in.
MAAS operates under the assumption that MAC addresses of physical NICs are unique. If that's not the case for devices such as routers or switches and multiple ports can legitimately have the same MAC address, MAAS will need to relax the uniqueness constraint for devices.