Bug 2178645 - Error importing repositories with GPG key
Summary: Error importing repositories with GPG key
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.12.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.14.0
Assignee: Adam Ruzicka
QA Contact: David Moore
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-15 14:06 UTC by Joniel Pasqualetto
Modified: 2023-07-07 15:56 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2190512 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36185 0 Normal Closed Content View import fails with 'Tried to load unspecified class: Sequel::SQL::Blob' 2023-04-04 17:51:16 UTC
Github Dynflow dynflow pull 426 0 None Merged Cast sequel blobs back to strings 2023-04-04 17:51:16 UTC
Red Hat Issue Tracker SAT-16523 0 None None None 2023-03-16 14:17:07 UTC
Red Hat Knowledge Base (Solution) 7006713 0 None None None 2023-04-07 09:30:31 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.