missing 'builder' permission in archiveuploader

Bug #672931 reported by Jelmer Vernooij
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jelmer Vernooij

Bug Description

Some uploads are still getting stuck in UPLOADING despite the recent fix to transaction.commit() early, because they are attempting to access the builder table.

As far as I can tell this should be fixable by adding read access to builder in archiveuploader.

Tags: lp-soyuz qa-ok

Related branches

Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in soyuz:
milestone: none → 10.11
tags: added: qa-needstesting
Changed in soyuz:
status: Triaged → Fix Committed
Jelmer Vernooij (jelmer)
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Robert Collins (lifeless) wrote :

Needs a deploy to the relevant machines.

Changed in soyuz:
status: Fix Committed → Fix Released
status: Fix Released → Fix Committed
Curtis Hovey (sinzui)
Changed in soyuz:
status: Fix Committed → Fix Released
Revision history for this message
Aaron Bentley (abentley) wrote :

This appears fixed, and old builds stuck in "uploading" have been switched to "failed to upload". Please report any further instances of this problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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