Bug 2178645

Summary: Error importing repositories with GPG key
Product: Red Hat Satellite Reporter: Joniel Pasqualetto <jpasqual>
Component: Inter Satellite SyncAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: David Moore <damoore>
Severity: medium Docs Contact:
Priority: high    
Version: 6.12.1CC: ahumbe, damoore, jbhatia, msunil, nmohite, pcreech, saydas, vsedmik
Target Milestone: 6.14.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2190512 (view as bug list) Environment:
Last Closed: 2023-11-08 14:18:58 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 Joniel Pasqualetto 2023-03-15 14:06:04 UTC 
Description of problem:

Trying to import a repository that includes GPG key, fails with the error below:

]# hammer content-import repository --path $(pwd) --organization-id 1
[.........................................................................................                                                                                                                                            ] [39%]
Error: Tried to load unspecified class: Sequel::SQL::Blob

Version-Release number of selected component (if applicable):
Satellite 6.12

How reproducible:
Always

Steps to Reproduce:
1.Create a custom repository
2. Create a content certificate of type GPG key and assign to custom repository
3. Sync the repository
4. Export the repository 
5. Try importing the exported repository into a Satellite

Actual results:
Import fails 

Expected results:
Import task would run and bring the GPG key AND the content to the disconnected Satellite


Additional info:
As workaround, one could remove the GPG key from the connected server, export the repository without the key and then create the key manually on the disconnected Satellite and then assign to the repo.
Comment 9 Bryan Kearney 2023-04-04 20:03:26 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36185 has been resolved.
Comment 15 errata-xmlrpc 2023-11-08 14:18:58 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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818