Start-up stacktrace: IntegrityError: duplicate key value violates unique constraint "maasserver_config_name_uniq" DETAIL: Key (name)=(rpc_shared_secret) already exists.
Bug #1459168 reported by
Raphaël Badin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Critical
|
Unassigned | ||
Bug Description
(Apparently) inconsequential start-up stacktrace: http://
Related branches
lp:~allenap/maas/database-locks-rererevisited
- Blake Rouse (community): Approve
-
Diff: 247 lines (+60/-75)4 files modifiedsrc/maasserver/dns/config.py (+3/-7)
src/maasserver/dns/tests/test_config.py (+16/-29)
src/maasserver/locks.py (+2/-2)
src/maasserver/security.py (+39/-37)
Revision history for this message
| Gavin Panella (allenap) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Gavin Panella (allenap) |
| status: | Triaged → In Progress |
Revision history for this message
| Gavin Panella (allenap) wrote | #2 |
| Changed in maas: | |
| status: | In Progress → Invalid |
| assignee: | Gavin Panella (allenap) → nobody |
To post a comment you must log in.
I think this is a side-effect of decreasing transaction isolation from SERIALIZABLE to REPEATABLE READ.