GitRepository:+permissions fails constraint validation if an invisible private team has a grant

Bug #1927979 reported by Alberto Donato
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

OOPS-d45956a4448f3531b148df3155425529

Accessing https://code.launchpad.net/~maas-committers/maas/+git/maas/+permissions I get a 500 error, despite being member of the ~maas-committers team.

Revision history for this message
Björn Tillenius (bjornt) wrote :

I also seen an OOPS trying to view that page: OOPS-35dd42e8c97115abcd63e9d2f3f67750

Revision history for this message
Colin Watson (cjwatson) wrote :

The issue is that a particular private team has permissions on that repository, but only a subset of the repository owners can see that private team. We'll need to adjust the constraint on `GitGranteeField` somehow so that any current grantee is accepted even if it wouldn't normally be available for selection due to the constraints imposed by the `ValidPersonOrTeam` vocabulary.

tags: added: lp-code oops privacy ui
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Colin Watson (cjwatson)
summary: - 500 error accessing project sharing page
+ GitRepository:+permissions fails constraint validation if invisible
+ private team has a grant
summary: - GitRepository:+permissions fails constraint validation if invisible
+ GitRepository:+permissions fails constraint validation if an invisible
private team has a grant
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.