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