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.
Description of problem:
=======================
Content credentials (e.g. GPG keys) that are in use by products or repositories in Satellite 6.x can be deleted. We need to implement a safety mechanism to prevent this from happening, and only allow content credentials that are no longer in use to be deleted.
Version-Release number of selected component (if applicable):
=============================================================
Red Hat Satellite 6.8, 6.9 and 6.10
How reproducible:
=================
Always
Steps to Reproduce:
===================
1. Create a GPG key in Red Hat Satellite's web UI under Content --> Content Credentials.
2. Create a custom product/repository in Red Hat Satellite's web UI, and configure it to use the GPG key created in step (1).
3. Go back to Content --> Content Credentials and deleted the GPG key.
Actual results:
===============
The GPG key is deleted.
Expected results:
=================
As the GPG key is still in use by an existing product/repository, the deletion of the GPG key should be blocked.
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.13 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-2023:2097