Bug 1537555
Summary: | Cannot remove GPGkey from client repo | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sean O'Keeffe <sokeeffe> |
Component: | Content Credentials | Assignee: | Justin Sherrill <jsherril> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | Unspecified | CC: | arusso, aymeric.marchal, bkearney, gscarbor, inecas, jalviso, james.xue, karnsing, pcreech, rraghuwa, satellite6-bugs, saydas, vdeshpan, vijsingh |
Target Milestone: | 6.7.0 | Keywords: | 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: | Environment: | ||
Last Closed: | 2020-04-14 13:22:23 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
Sean O'Keeffe
2018-01-23 13:47:01 UTC
The only workaround I found was "subscription-manager repo-override --repo <REPOID> --add gpgcheck:0" Connecting redmine issue https://projects.theforeman.org/issues/15087 from this bug Just wanted to update that I can confirm that this issue is present in 6.4 as well. The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you. Verified in Satellite 6.7 snap 9 create a yum repo create a content credential of a gpg key (any contents work) register a system with sub-man and subscribe it to the yum repo notice in /etc/yum.repos.d/redhat.repo there is no gpg key Associate the gpg key with the repository on the repo details page run sub-man refresh && yum repolist notice in /etc/yum.repos.d/redhat.repo there is a gpg key for the repo Remove the gpg key from the repo on the repo details page run sub-man refresh notice in /etc/yum.repos.d/redhat.repo thegpg key for the repo is now gone. 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, 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-2020:1454 |