REGRESSION: Build histories for buildds that have built private builds give a 403 for buildd-admins and above

Bug #301541 reported by Sarah Kowalik
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Julian Edwards

Bug Description

For buildd admins and above, it appears that the buildds that have built private builds show a 403 error when a private build appears on the build history listing. This does not affect mere mortals (either logged in or not).

Such URLs include:

https://edge.launchpad.net/+builds/hooker/+history
https://edge.launchpad.net/+builds/kohnen/+history
https://edge.launchpad.net/+builds/artigas/+history

(depending on when you view these links, you may need to go further through the list of builds)

The result is:
Not allowed here

Sorry, you don't have permission to access this page.

You are logged in as Sarah Hobbs.

Tags: lp-soyuz
description: updated
Changed in soyuz:
assignee: nobody → julian-edwards
importance: Undecided → Medium
milestone: none → 2.1.12
status: New → Triaged
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote :

RF 7338

Sorry 'bout that.

Changed in soyuz:
status: In Progress → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
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.