Database errors in a BranchScanJob cause the advisory lock release to crash
Bug #1039638 reported by
Aaron Bentley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
A scan of ~canonical-
This is a database error, "current transaction is aborted, commands ignored until end of transaction block", which means we don't see the root cause.
The database error is happening because we try to unlock an advisory lock when the current transaction is in a failed state. Instead, we should abort the transaction. Once the masking error is dealt with, we may be able to determine the root cause.
~exaile-
description: | updated |
To post a comment you must log in.
Bug #1040777 was a dupe of this which I used to handle the underlying issue (a missing SELECT permission on accesspolicygrant). I guess this bug can be repurposed to fix the advisory lock crash which masked the real issue.
https:/ /pastebin. canonical. com/73021/ is helpful to reveal the underlying exception.