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: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.11.0CC: ahumbe, paji
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, 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: 2024-06-06 12:56:44 UTC 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.
Comment 3 Eric Helms 2024-06-06 12:56:44 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.