Project

Profile

Help

Issue #7709

closed

Add EPEL fails due to GPG signature validation (when run against RHEL, and thus using the https URL)

Added by bmbouter almost 2 years ago. Updated almost 2 years ago.

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:

Actions #1

Updated by spredzy almost 2 years ago

  • Assignee set to spredzy

Added by spredzy almost 2 years ago

Revision 9d94b5d0

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

Added by spredzy almost 2 years ago

Revision 9d94b5d0

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

Actions #2

Updated by pulpbot almost 2 years ago

  • Status changed from NEW to POST
Actions #3

Updated by spredzy almost 2 years ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by ttereshc almost 2 years ago

  • Sprint/Milestone set to 3.8.0
Actions #5

Updated by ttereshc almost 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF