Actions
Issue #7709
closed
Add EPEL fails due to GPG signature validation (when run against RHEL, and thus using the https URL)
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
This is needed to resolve https://github.com/ansible/galaxy_ng/issues/515#issuecomment-708360555
Added by spredzy about 4 years ago
Added by spredzy about 4 years ago
Revision 9d94b5d0 | View on GitHub
EPEL: Import GPG keys
An issue in ansible[1] has been fixed ensuring that the dnf/yum module actually does verify GPG signature. Meaning we need to import them before using epel.
[1] https://github.com/ansible/ansible/pull/71537
fixes: #7709
Updated by pulpbot about 4 years ago
- Status changed from NEW to POST
Updated by spredzy about 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp|9d94b5d038dbe83ebe40759886941c0b19d07b96.
Updated by ttereshc about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
EPEL: Import GPG keys
An issue in ansible[1] has been fixed ensuring that the dnf/yum module actually does verify GPG signature. Meaning we need to import them before using epel.
[1] https://github.com/ansible/ansible/pull/71537
fixes: #7709