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

When importing the content in a disconnected satellite, the customer is facing "Error: 502 Bad Gateway"

XMLWordPrintable

    • Phoenix - Subscriptions
    • 0
    • False
    • Important
    • None
    • None
    • None
    • No Coverage

      Description of problem:
      When importing the content in a disconnected satellite that was exported from a connected one, the customer is facing "Error: 502 Bad Gateway"

      [root@walldisconnected httpd]# time hammer content-import library --organization="ACME" --path=/var/lib/pulp/imports/2022-12-20T01-59-43-00-00
      [......................................................... ] [26%]
      Could not import the archive.:
      Error: 502 Bad Gateway

      real 135m46.055s
      user 0m48.984s
      sys 0m8.540s

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

      How reproducible:
      100%

      Steps to Reproduce:
      1. Install Satellite, enable and sync rhel8 baseOS and AppStream (here as immediate)
      2. Export the content via hammer
      3. Import the content via hammer in the disconnected satellite

      Actual results:
      The hammer command it's always failing. However, the task is still running and will conclude the import process after some hours

      Expected results:
      The hammer command be there with no issues until the last minute

      Additional info:
      One workaround is, pass "-async" in the hammer command, then the customer can follow the task, but the regular command without "-async" should works as well.

              jira-bugzilla-migration RH Bugzilla Integration
              rhn-support-wpinheir Waldirio Pinheiro
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: