Bug 814118
| Summary: | Katello doesn't update candlepin product content on gpgkey data change | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Garik Khachikyan <gkhachik> | ||||
| Component: | Content Management | Assignee: | Justin Sherrill <jsherril> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Katello QA List <katello-qa-list> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0.0 | CC: | alikins, asettle, bkearney, cpelland, daviddavis, dmacpher, mkoci, mmccune, omaciel | ||||
| Target Milestone: | Unspecified | Keywords: | Regression, Triaged, ZStream | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Adding a GPG key to a product repository after creation did not properly set the "gpgcheck" configuration option in the client's repo file. This fix regenerates changed content and updates configuration when updating the GPG key.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 827554 (view as bug list) | Environment: | |||||
| Last Closed: | 2012-10-09 19:17:56 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: | |||||||
| Bug Depends On: | 834125 | ||||||
| Bug Blocks: | 827554 | ||||||
| Attachments: |
|
||||||
|
Description
Garik Khachikyan
2012-04-19 09:32:59 UTC
Created attachment 579037 [details]
pem files
sending in a tarball.
1596817263600090748.pem
1596817263600090748-key.pem
There does not appear to be a gpgkey set in those entitlement certs, so at least for those certs, subscription-manager appears to be doing the right thing. The entitlement cert doesn't actually have a gpg key url set in it. I just ran a quick test on a katello install, and it looks like if you change the gpgkey url on an existing repository, that change is never propagated down to candlepin. Creating a repository with a gpg key set originally gets the key url into candlepin, and thus into the entitlement cert. Reassigning to katello. setting to 1.0.z since the implications of this are fairly severe Hrmmm I have not been able to reproduce the original scenario with katello master and the latest rhsm from 6.2 or the version that Garik mentioned. In both cases gpgcheck is set to 1. Garik, Which version of katello did you find this with? Still going to address the issue where you enable/disable the gpg key on an existing repo. fixed in katello master: 604d36ae7c6056d6559d64cdba94422cc68f3ec5 This is going to fail. For more info see https://bugzilla.redhat.com/show_bug.cgi?id=824581 which has the most up-to-date information. Rather, it's not going to fail but gpgkey will be set in the repo file while gpgcheck will still be 0. Pull request: https://github.com/Katello/katello/pull/729 Commit SHA: a609539ac3b4f9f72c155f15b7521ad4bfd1f429 the above code was actually reverted and the fix was implemented within Candlepin itself. This bug looks largely like a dupe of: https://bugzilla.redhat.com/show_bug.cgi?id=824581 which we have as VERIFIED. If QE wants to re-test this go ahead. this is also blocked by: https://bugzilla.redhat.com/show_bug.cgi?id=834125 Talk to Og and are going to close this as a dupe *** This bug has been marked as a duplicate of bug 824581 *** |