Bug 2155644

Summary: When importing the content in a disconnected satellite, the customer is facing "Error: 502 Bad Gateway"
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: Inter Satellite SyncAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.11.0CC: ahumbe, paji
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2022-12-21 17:36:36 UTC 
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.