Bug 1277363 - 502 Proxy Error when changing several bugs at once
502 Proxy Error when changing several bugs at once
Status: CLOSED DUPLICATE of bug 1282925
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
Depends On:
  Show dependency treegraph
Reported: 2015-11-03 02:22 EST by Rohan McGovern
Modified: 2016-06-15 22:23 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-06-15 22:23:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rohan McGovern 2015-11-03 02:22:26 EST
Description of problem:
If I navigate to a large bug list and use the "Change Several Bugs at Once" feature to add a comment and change the status of all the bugs, after submitting, the page tries to load for a while and eventually stops with:

502 Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /process_bug.cgi.

Reason: Error reading from remote server

There is no indication whether my changes were applied, in full or partially.

Version-Release number of selected component (if applicable):

How reproducible:
unknown; probably easy to reproduce with >100 bugs

Steps to Reproduce:
1. Navigate to a bug list with >100 bugs
2. Click "Change Several Bugs at Once"
3. In the form, enter a comment, and select a status
4. Submit

Actual results:
Browser waits for a response for a while, then renders 502 Proxy Error.

Expected results:
Response is successfully rendered and/or progress is somehow reported asynchronously.

Additional info:
The specific bug list where I've most recently seen this is this one, with 102 bugs:

Comment 1 Matt Tyson 2015-11-03 18:31:39 EST
We have a 2 minute (IIRC) timeout which will kill any long running HTTP connections.

Bulk changes should continue to run in the background.

This is to prevent excessive load on the system.

The only workaround I can offer is to perform the updates in smaller chunks or just trust that the process worked, despite the 502 error.

> progress is somehow reported asynchronously.

I think bugzilla 5.0 has this feature, but the proxy timeout limit will still apply.
Comment 2 Jeff Bastian 2015-11-23 17:49:53 EST
I hit this with the bugzilla command line tool, too, while trying to close about 60 old bugs that are no longer valid.

$ bugzilla modify -l "Closing as CURRENTRELEASE" \
           -k CURRENTRELEASE $(bugzilla query -p Acadia -t ON_QA \
                                      --fixed_in="3" --outputformat='%{id}')
Connection lost/failed: 502 Server Error: Proxy Error
Comment 3 Jeff Fearn 2016-06-15 22:23:17 EDT

*** This bug has been marked as a duplicate of bug 1282925 ***

Note You need to log in before you can comment on or make changes to this bug.