Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-9409

BZ#2035873 Concurrent CV Publish fails with 502 error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • SAT QE - Bugzilla
    • None
    • QE Sprint 9, QE Sprint 10
    • None

      https://bugzilla.redhat.com/show_bug.cgi?id=2035873 - Description of problem:
      Concurrent / Parallel CV publishing failed with error -
      ```
      <title>502 Proxy Error</title>
      </head><body>
      <h1>Proxy Error</h1>
      <p>The proxy server received an invalid
      response from an upstream server.<br />
      The proxy server could not handle the request <em><a href="/pulp/api/v3/content/rpm/packages/">GET /pulp/api/v3/content/rpm/packages/</a></em>.<p>
      Reason: <strong>Error reading from remote server</strong></p></p>
      </body></html>
      Error message: the server returns an error
      HTTP status code: 502
      ```

      Version-Release number of selected component (if applicable):
      Satellite 7.0 snap 3

      How reproducible:

      Steps to Reproduce:
      1. Sync 5 big RHEL repos from CDN using subscription.
      2. Create 6 CVs (satellite has 6 workers since I had 6 cores in satellite server) with each containing all 5 repos from step 1.
      3. Start publishing 6 CVs in parallel.

      Actual results:
      All 6 CVs publishing errored with the same error as mentioned in the description of the bug.

      Expected results:
      All 6 CVs publishing should be successful using 6 pulp workers without error!

      Additional info:

      The stack trace from a CV-
      ```
      Error message: the server returns an error
      HTTP status code: 502
      Response headers:

      {"Date"=>"Mon, 27 Dec 2021 15:26:35 GMT", "Server"=>"Apache", "Content-Length"=>"445", "Content-Type"=>"text/html; charset=iso-8859-1"}

      Response body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      <html><head>
      <title>502 Proxy Error</title>
      </head><body>
      <h1>Proxy Error</h1>
      <p>The proxy server received an invalid
      response from an upstream server.<br />
      The proxy server could not handle the request <em><a href="/pulp/api/v3/content/rpm/packages/">GET /pulp/api/v3/content/rpm/packages/</a></em>.<p>
      Reason: <strong>Error reading from remote server</strong></p></p>
      </body></html>
      Error message: the server returns an error
      HTTP status code: 502
      Response headers:

      {"Date"=>"Mon, 27 Dec 2021 15:25:43 GMT", "Server"=>"Apache", "Content-Length"=>"445", "Content-Type"=>"text/html; charset=iso-8859-1"}

      Response body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      <html><head>
      <title>502 Proxy Error</title>
      </head><body>
      <h1>Proxy Error</h1>
      <p>The proxy server received an invalid
      response from an upstream server.<br />
      The proxy server could not handle the request <em><a href="/pulp/api/v3/content/rpm/packages/">GET /pulp/api/v3/content/rpm/packages/</a></em>.<p>
      Reason: <strong>Error reading from remote server</strong></p></p>
      </body></html>
      Error message: the server returns an error
      HTTP status code: 502
      Response headers:

      {"Date"=>"Mon, 27 Dec 2021 15:25:42 GMT", "Server"=>"Apache", "Content-Length"=>"445", "Content-Type"=>"text/html; charset=iso-8859-1"}

      Response body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      <html><head>
      <title>502 Proxy Error</title>
      </head><body>
      <h1>Proxy Error</h1>
      <p>The proxy server received an invalid
      response from an upstream server.<br />
      The proxy server could not handle the request <em><a href="/pulp/api/v3/content/rpm/packages/">GET /pulp/api/v3/content/rpm/packages/</a></em>.<p>
      Reason: <strong>Error reading from remote server</strong></p></p>
      </body></html>
      ```

            jyejare Jitendra Yejare
            jira-bugzilla-migration RH Bugzilla Integration
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: