MAAS

[2.0b5] duplicate key on startup: Key (vid, fabric_id)=(2, 0) already exists.

Bug #1583333 reported by LaMont Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Gavin Panella
MAAS 2.0.0

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 modified
src/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)
Revision history for this message
LaMont Jones (lamont) wrote :
Revision history for this message
LaMont Jones (lamont) wrote :

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...

summary: - duplicate key on startup: Key (vid, fabric_id)=(2, 0) already exists.
+ [2.0b5] duplicate key on startup: Key (vid, fabric_id)=(2, 0) already
+ exists.
Revision history for this message
LaMont Jones (lamont) wrote :

2.0.0~beta5+bzr5026-0ubuntu1~xenial1

Revision history for this message
LaMont Jones (lamont) wrote :

However.... After the last regiond comes up, the rack reports that it is missing a regiond connection.

Gavin Panella (allenap)
Changed in maas:
assignee: nobody → Gavin Panella (allenap)
status: New → In Progress
Blake Rouse (blake-rouse)
Changed in maas:
milestone: none → 2.0.0
importance: Undecided → Critical
importance: Critical → High
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
LaMont Jones (lamont) wrote :

This trace was with rev 5134.. To be fair, it was a failure that occurred on the 130th iteration of "purge all of maas, remove the dependencies, drop the database, and reinstall."

Revision history for this message
Gavin Panella (allenap) wrote :

That error comes from _process_sys_info, which does not run with the rack_registration lock. The recently landed lp:~allenap/maas/retry-integrity-errors branch ought to resolve these kinds of problems generally (meaning we could remove the rack_registration lock now, but it probably reduces the number of collisions and so still has some worth).

Andres Rodriguez (andreserl)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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