Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
Running migration on a fairly large db can get the "HTTP status code: 502"

Version-Release number of selected component (if applicable):
6.9.0 snap 17

Steps to Reproduce:
1. Run migration command on a large db, something like dogfood

Actual results:
HTTP status code: 502

Expected results:
Migration should finish successfully.

Additional info:
There's a workaround with changing the bulk_load_size to 500 that resolves this.

Connecting redmine issue https://projects.theforeman.org/issues/32112 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32112 has been resolved.

Steps to retest
1. Run migration command on a large db, something like dogfood

Expected:
Migration should finish successfully

Actual:
Migration finished successfully

This issue was initially discovered on dogfood server.  I have ran dogfood server on new build and it has completed migration successfully without issues.

Verified on 6.9.0_019.1 on foreman-installer-2.3.1.10-1.el7sat.noarch

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1313