Duplicate interfaces causing rack controller not to register
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
I did a fresh install of 2.5.1-7489-
After the install finished, there's a notice that once rack controller isn't connected to the region. Looking at the controller page, it says that rackd is 25% connected.
I see this in the regiond.log:
maasserver.
I see that somehow I do have two physical interfaces with the same mac address and name. Not sure how it got there, though:
maasdb=# select id, mac_address, name, node_id, type, vlan_id from maasserver_in
terface;
id | mac_address | name | node_id | type | vlan_id
----+--
1 | 00:16:3e:7c:bf:ee | eth0 | 1 | physical | 5001
2 | 00:16:3e:a0:b9:39 | eth1 | 1 | physical | 5002
4 | 52:54:00:b0:5e:8d | virbr0 | 1 | bridge | 5003
5 | 6e:65:9f:c2:31:e2 | br0 | 1 | bridge | 5001
6 | 66:4b:16:ec:b3:d0 | br1 | 1 | bridge | 5002
3 | 52:54:00:fe:18:d6 | mpqemubr0-dummy | 1 | physical | 5004
7 | 52:54:00:fe:18:d6 | mpqemubr0 | 1 | bridge | 5004
8 | 00:16:3e:7c:bf:ee | eth0 | 1 | physical |
9 | 00:16:3e:a0:b9:39 | eth1 | 1 | physical |
10 | 52:54:00:fe:18:d6 | mpqemubr0-dummy | 1 | physical |
(10 rows)
Related branches
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 146 lines (+109/-0)3 files modifiedsrc/maasserver/migrations/maasserver/0197_remove_duplicate_physical_interfaces.py (+55/-0)
src/maasserver/migrations/maasserver/0198_interface_physical_unique_mac.py (+20/-0)
src/maasserver/models/tests/test_interface.py (+34/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
status: | Triaged → Confirmed |
milestone: | none → 2.5.1 |
no longer affects: | maas/2.6 |
Changed in maas: | |
milestone: | 2.5.1 → 2.6.0 |
Changed in maas: | |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
milestone: | 2.6.0 → 2.7.0alpha1 |
status: | Confirmed → In Progress |
no longer affects: | maas/2.5 |
no longer affects: | maas/2.6 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
I've hit the same issue but in MAAS 2.6.0 (7802-g59416a86 9-0ubuntu1~ 18.04.1) configured without MAAS HA. The uploaded logs are the same in my case.