BugWatch updates on the Redhat Bugzilla are chronically broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Critical
|
Steve Kowalik |
Bug Description
It appears that all Redhat Bugzilla watches are broken because of the following error when calling getModifiedRemo
Fault: <Fault 10000: 'Your query returned 318245 bugs and Red Hat Bugzilla will only return\\n100000 or less bugs. Please back up and narrow your search criteria. If\\nyou feel your results were expected and your search criteria was\\ncorrect, please send email to <email address hidden> describing what\\nyou were doing and we will correct the error.'>
This is probably happening because the oldest lastchecked date is some time in the past (we certainly don't have 31,000 watches). However, this in itself is strange because we usually pass a set of bug IDs to the remote system (as in 'which of these bugs have changed since this date?').
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: story-reliable-bug-syncing |
Changed in launchpad: | |
importance: | High → Critical |
tags: | added: oops |
tags: | added: bugwatch |
A first step would be to get a solid trace of the query we make. Adding this to the timeline should be straight forward.