Bug 2155644 - When importing the content in a disconnected satellite, the customer is facing "Error: 502 Bad Gateway"
Summary: When importing the content in a disconnected satellite, the customer is facin...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.11.0
Hardware: All
OS: All
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-21 17:36 UTC by Waldirio M Pinheiro
Modified: 2023-07-20 21:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19088 0 None None None 2023-07-20 21:21:51 UTC

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.


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