[2.0b5] duplicate key on startup: Key (vid, fabric_id)=(2, 0) already exists.
Bug #1583333 reported by
LaMont Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Gavin Panella |
Bug Description
Upon fresh install, there were errors logged about unique-constraint violations. This rack-n-region controller has br0 which has eth0.2 as its only member at the time (br0 is used to bridge vms into the right vlan.)
Related branches
lp:~allenap/maas/duplicate-vlan-on-start--bug-1583333
- Blake Rouse (community): Approve
-
Diff: 675 lines (+243/-147)8 files modifiedsrc/maasserver/locks.py (+11/-1)
src/maasserver/models/node.py (+7/-0)
src/maasserver/models/tests/test_node.py (+20/-0)
src/maasserver/rpc/rackcontrollers.py (+78/-70)
src/maasserver/rpc/regionservice.py (+4/-7)
src/maasserver/rpc/testing/fixtures.py (+9/-11)
src/maasserver/rpc/tests/test_rackcontrollers.py (+110/-58)
src/maasserver/rpc/tests/test_regionservice.py (+4/-0)
Changed in maas: | |
assignee: | nobody → Gavin Panella (allenap) |
status: | New → In Progress |
Changed in maas: | |
milestone: | none → 2.0.0 |
importance: | Undecided → Critical |
importance: | Critical → High |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This log is from at (or shortly after) the point where maas claimed that only 3 regionds were running, rather than the 4 that were expected.
This does self correct in the first few minutes of the , so it's not super criticial...