Fix GPG key import for a large set of DeepOps roles #1184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ajdecon
changed the title
dholt
approved these changes
Jun 16, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Previously, many DeepOps roles were importing the full Fedora GPG keychain from
https://getfedora.org/static/fedora.gpg. At some point in the past several days, this started failing with errors that look like this:Unfortunately, it's difficult to tell what may have changed with the upstream URL.
Because we're just interested in EPEL anyway, this PR changes the URL import to the EPEL-specific key for the distro in question, i.e.
https://download.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-{{ ansible_distribution_major_version }}.Test plan
All Molecule tests should pass following this change. (Jenkins CI is still broken 😢 for other reasons around a Helm chart.)