Description of problem: After upgrading from Katello 4.2 to 4.3 (Satellite 6.10 to 7.0 essentially), some upstream users are encountering sync problems with some repositories. A 500 error is triggered when the /repositories/.../sync/ endpoint is used. The error seems to be related to the client_cert / client_key / ca_cert values. Version-Release number of selected component (if applicable): Satellite 7.0 How reproducible: It's unclear how to reproduce Steps to Reproduce: N/A for now Actual results: 500 for sync request with some remotes Expected results: 200 for sync request Additional info: Related community thread: https://community.theforeman.org/t/pulprpmclient-apierror-http-500-during-sync-repository/27480/13
It sounds like the repair script from the PR won't need to be run in Satellite because the migration issue will be fixed. Only upstream users who upgraded to Katello 4.3 without the fix will need to run the repair script.
Correct. However Satellite does need to upgrade to pulpcore 3.16.6 or 3.17.6 to avoid being impacted - the current snap has 3.16.3
Tested by syncing several rhel repos and syncing several remote repos. Run the upgrade job. The job was successful. Here's the result: https://satqe-jenkins-csb-satellite-qe.apps.ocp-c1.prod.psi.redhat.com/view/6.11%20Upgrade/job/sat-6.11-rhel7-y_stream-upgrade-testing/6/console Since this is already tested upstream and we have upgrade jobs already in place, this was more or less a regression test run. Also, it's difficult to test fully. Tested with 6.10.7 and upgraded to 6.11.0 snap 25 with tfm-pulpcore-python3-pulpcore-3.16.8-2.el7pc.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.11 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-2022:5498