Description of problem: I have been using the XML-RPC interface to bugzilla to change the status of rhel-5 kernel bugs to MODIFIED. When I try to change anything less than (around) 13 bugs, it usually works (just takes a looong time, ie 10 minutes or so and the XML-RPC times out, but that's another issue). However, it seems anything over 13 (this is a rough number) only about 13 bugs are modified and the rest sit in their original status. I have to take the new list and re-try setting them to MODIFIED. This usually works after a few tries. My problem is I usually batch my commits and check them in around 20 at a time (just because of the influx of patches, its hard sometimes to do less and keep up). So I run into this alot. I don't like the gui because currently i have everything automated from changelog to cvs commit to bugzilla state MODIFIED. Version-Release number of selected component (if applicable): current bugzilla. How reproducible: reliably Steps to Reproduce: 1. using the perl XML-RPC system.multicall, batch about 20 commands together 2. wait until it times out 3. wait some more 4. check status of bugs Actual results: Expected results: Additional info:
Don't you get a return status that allows you to see whether the call was successful or not? Dave, could you please help us with this?
Unfortunately the system.multicall does not return a success/fail code until all calls are completed successfully. That is the nature of XMLRPC itself. It only prints the data structure containing the response at the very end. Have you tried just calling bugzilla.changeStatus() from your client multiple times instead of using system.multicall? This may should you if one or more are failing somewhere or which bugs are taking the longest. Remember some bugs are part of blocker bugs and alot of processing is required to notified all people attached to each of the bugs. Single bugs not connected to other bugs with only a few email recipients should process rather quickly.
Calling bugzilla.changeStatus multiple times is probably a good work around. I just suck at writing perl so while converting from a system.multicall isn't too difficult (modify the loop to instead of pushing to execute the call). But collecting the output so I can display it might give me indigestion (maybe I don't care for output though..). Thanks.
The only thing i thing that gets returned is who was/wasn't emailed about the change. So you typically just ignore that. perl code would look like: use XMLRPC::Lite; use Data::Dumper; my @bugids = [1434,34554,34553] my @results = (); my $rpc = new XMLRPC::Lite (proxy=>'https://bugzilla.redhat.com/bugzilla/zmlrpc.cgi'); foreach my $id (@bugids) { my $call = $rpc->call('bugzilla.changeStatus', 'MODIFIED', $username, $password); push (@results, $call->result); } print Dumper(\@results);
Thanks, I'll give that a whirl..
Closing this bug now as DEFERRED, as it is an issue we should look at in future.