This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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: CLOSED MIGRATED
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: 2024-06-06 12:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:56:44 UTC
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 Migrated None 2024-06-06 12:56:43 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.
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.
Note You need to log in before you can comment on or make changes to this bug.