Database errors in a BranchScanJob cause the advisory lock release to crash

Bug #1039638 reported by Aaron Bentley
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

A scan of ~canonical-hw-cert/checkbox-editor/trunk failed with OOPS-20a29e8a7bf4295727dddba3ddb75792

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-devel/exaile/exaile-0.3.x is also affected: OOPS-677efac4bada8fc088486a052a01e0ce

Aaron Bentley (abentley)
description: updated
Revision history for this message
William Grant (wgrant) wrote :

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.

summary: - Scans of ~canonical-hw-cert/checkbox-editor/trunk oops with a database
- error
+ Database errors in a BranchScanJob cause the advisory lock release to
+ crash
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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