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.

Bug 2064400

Summary:	Migration of encrypted fields between 3.14 and 3.16 is broken for some remotes
Product:	Red Hat Satellite	Reporter:	Ian Ballou <iballou>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Lai <ltran>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	dalley, dkliban, ggainey, rchan, wpinheir
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pulpcore-3.16.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:34:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ian Ballou 2022-03-15 18:18:58 UTC

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

Comment 1 Ian Ballou 2022-03-16 16:18:04 UTC

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.

Comment 3 Daniel Alley 2022-03-26 00:33:00 UTC

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

Comment 7 Lai 2022-06-14 15:58:07 UTC

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

Comment 10 errata-xmlrpc 2022-07-05 14:34:27 UTC

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