what happens when the xmlrpc calls fail between Bugzilla & Issue Tracker and
Is the data left in an inconsistent state?
Could we queue failed queries up in a database table that a cron job could pick
up and run later on?
evaluate & add documentation (in Bz in the perldoc) about the impact of failure
when xmlrpc fails to IT. Evaluate if we are handling these situations correctly.
Subject: Re: [engineering.redhat.com #13889]
Date: Fri, 13 Jul 2007 15:03:41 -0400
From: Lisa Davidson <email@example.com>
From I-T to BZ, when an event is propagated to BZ successfully, a record
is recored in a table. On I-T UI, it will display in this format to the
event sent to $bug $at_this_time by $this_user as $private/$public
Once an event is sent successfully, I-T user can't propagate the event
to the same bug any more.
If an event failed t propagate to BZ, I-T errors end user on the web UI.
It will allow the end user to try as many time as they want to until it
Regarding the failed IT score update, there is a nightly cron job to
There is an idea of storing failed xmlrpc calls in a table for later process by
a cron job.
EVAL callIT( @args )
queueCallITlater( @args )
later in a cron space far away
FOR each queued IT call
IF call has to many errors THEN
notify bugzilla maintainer
EVAL callIT( @args )
IF failed THEN
leave on queue for a later run
remove from queue
We could create a queue table that has all of the columns/values of the key
value pairs that we send to IT. But if add/remove key/value pairs later on this
may be a hassle. We could just create a queue table with bug_id, it_id,
last_attempt_date, num_tries, data where data is a TEXT column with Data::Dumper
structure of the data we were trying to
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and
therefore this feature will need to be implemented against the new release.
Updating bug version to 3.2.
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can.
Bugzilla Development Team
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.
If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.
Thanks, the Bugzilla team.
Closing inactive bugs are part of Bugzilla cleanup.