Bad TeamParticipation data (oops +particpation)

Bug #699842 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
j.c.sackett

Bug Description

These oopses show some users were not fixed by the recent fix the TP data.

  15 KeyError: <Person at INSTANCE-ID locoteams (Ubuntu Local Community Teams)>
       4 https://bugs.launchpad.net/~jtv/+participation (Person:+participation)
        OOPS-1832H2003, OOPS-1832L1711, OOPS-1832L1712, OOPS-1832M1728
       2 https://bugs.launchpad.net/~stub/+participation (Person:+participation)
        OOPS-1832E1251, OOPS-1832K1087

Tags: oops teams users
j.c.sackett (jcsackett)
Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
j.c.sackett (jcsackett) wrote :

I have a script that can generate a new TP data fix from the errors report, but the most recent report I've received doesn't any spurious TeamParticipation entries listed.

Also, looking at previous reports, jtv and stub weren't in list of users who had missing participation problems.

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

The oopses look like the same oopses as before. Maybe the script is wrong. If your script is using API, we may have discovered another victim of bug 680461 -- The method used by API is bad, it is discounting users we know are correct looking at +participation.

Revision history for this message
j.c.sackett (jcsackett) wrote :

My script just uses the spurious entries of the launchpad-errors mailing list. It's just a string munger. The last launchpad-errors email I got showed no spurious TeamParticipation entries.

I agree the oops looks to be the same, I am just not certain it is the same root cause. I am continuing to monitor the error emails--if I see spurious entries, I can generate a TP fix, but we will then know that there is something introducing new TP errors.

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

More interesting issues all with ~locoteams
2 https://edge.launchpad.net:3128/%7Embarnett/+participation (Person:+participation)
       OOPS-1833ED1231, OOPS-1833ED1718
4 https://bugs.launchpad.net/%7Emdz/+participation (Person:+participation)
        OOPS-1835A883, OOPS-1835E1021, OOPS-1835M889, OOPS-1835O870

Every +participation oops involves ~locoteams. Each person is also a canonical employee.
Maybe the script to fix the issue missed one path? I assume that stub and jtv could be in the same loco team, mbarnettt and mdz would be in different ones.

Changed in launchpad:
importance: High → Critical
Curtis Hovey (sinzui)
Changed in launchpad:
milestone: 11.01 → 11.02
j.c.sackett (jcsackett)
Changed in launchpad:
status: In Progress → 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.