Attempting to invite a private team fails with "Constraint not satisfied"

Bug #297833 reported by William Grant
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Edwin Grubbs

Bug Description

Attempting to invite a private team to (whether or not you have access to it) gives a "Constraint not satisfied" error.

Related branches

Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

The app needs to explain the private teams cannot be members of other teams.

Curtis Hovey (sinzui)
tags: added: oops
Changed in launchpad-registry:
milestone: none → 3.1.11
Revision history for this message
Martin Pool (mbp) wrote :

The description of this seems to be incorrect: you get this message even if you do have access to the team, eg if I try to add ~canonical to ~contributor-agreement-canonical. Or is that a different bug?

Changed in launchpad-registry:
assignee: nobody → Edwin Grubbs (edwin-grubbs)
Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: Triaged → In Progress
Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: 3.1.11 → 3.1.12
Revision history for this message
Karl Fogel (kfogel) wrote :

I second Martin's question from comment #2: when barry tried to add ~canonical to ~private-launchpad-strategy, he got this error as well.

See also bug #95193 ("Unhelpful error message adding team A as a member of team B when team B is already member of team A"), which has a similar symptom but a different cause.

Revision history for this message
Edwin Grubbs (edwin-grubbs) wrote :

Yes, this bug has nothing to do with whether you have access to a team. Rather, it stems from the fact that the item exists in the vocabulary, thus preventing an "Invalid value" error, but the PublicPersonChoice.constraint() method returns false for non-public teams. I have changed the constraint() to raise a more informative exception.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I am surprised that barry tried that, not to mention any launchpad developer tried that. Private teams cannot be members of other teams. The fix for the will land on edge in a few days. Since they cannot be members, I do not think bug #95193 is related in this case.

Revision history for this message
Edwin Grubbs (edwin-grubbs) wrote :

Yes, this bug has nothing to do with whether you have access to a team. Rather, it stems from the fact that the item exists in the vocabulary, thus preventing an "Invalid value" error, but the PublicPersonChoice.constraint() method returns false for non-public teams. I have changed the constraint() to raise a more informative exception.

description: updated
Revision history for this message
Barry Warsaw (barry) wrote :

@Curtis: I knew there was a reason it failed, I just couldn't remember the error!

Revision history for this message
Edwin Grubbs (edwin-grubbs) wrote : Bug fixed by a commit
Changed in launchpad-registry:
status: In Progress → Fix Committed
Changed in launchpad-registry:
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.