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.
DescriptionJoniel 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.
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