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

Bug #1583333 reported by LaMont Jones on 2016-05-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
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

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.
LaMont Jones (lamont) wrote :

2.0.0~beta5+bzr5026-0ubuntu1~xenial1

LaMont Jones (lamont) wrote :

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

Gavin Panella (allenap) on 2016-05-26
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
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."

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

Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers