P3A owned by a private team can't give subscriptions
Bug #597783 reported by
Joey Stanford
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Julian Edwards |
Bug Description
When an individual is given access to a P3A via subscription and the P3A's owner is a private team, not only do they get a "not allowed here" but they also become "locked out" from accessing any other P3As they have access to and are members of the team.
Related branches
lp:~julian-edwards/launchpad/p3a-sub-private-teams-bug-597783
- Henning Eggers (community): Approve (code)
- Māris Fogels (community): Approve
- Curtis Hovey (community): Approve (code)
-
Diff: 93 lines (+70/-1)2 files modifiedlib/canonical/launchpad/security.py (+13/-1)
lib/lp/soyuz/tests/test_archive_subscriptions.py (+57/-0)
tags: | added: oem-services |
affects: | launchpad → soyuz |
Changed in soyuz: | |
status: | Triaged → In Progress |
Changed in soyuz: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think this is actually because the owning team is private, not because of
the cascading nature of the subscription.