Another GPG error. I'm not sure why its failing on this host, it worked on my other host

Support
1

**======================================================================================================================================
Package Architecture Version Repository Size

Installing:
nagios-plugins-fping x86_64 2.4.9-1.el8 Default_Organization_EPEL_8_Everything_8_Everything_x86_64 48 k
Installing dependencies:
fping x86_64 4.2-2.el8 Default_Organization_Nagios_NCPA_nagiosxi-deps-el8 43 k
nagios-common x86_64 4.4.9-1.el8 Default_Organization_EPEL_8_Everything_8_Everything_x86_64 31 k
nagios-plugins x86_64 2.4.9-1.el8 Default_Organization_EPEL_8_Everything_8_Everything_x86_64 119 k

Transaction Summary

Install 4 Packages

Total download size: 240 k
Installed size: 414 k
Is this ok [y/N]: y
Downloading Packages:
(1/4): nagios-plugins-2.4.9-1.el8.x86_64.rpm 724 kB/s | 119 kB 00:00
(2/4): nagios-common-4.4.9-1.el8.x86_64.rpm 169 kB/s | 31 kB 00:00
(3/4): fping-4.2-2.el8.x86_64.rpm 226 kB/s | 43 kB 00:00
(4/4): nagios-plugins-fping-2.4.9-1.el8.x86_64.rpm 996 kB/s | 48 kB 00:00

Total 1.1 MB/s | 240 kB 00:00
nagiosxi-deps-el8 27 kB/s | 2.5 kB 00:00
GPG key at https://foreman.domain.com/katello/api/v2/repositories/4/gpg_key_content (0x45ECF0AD) is already installed
The GPG keys listed for the “nagiosxi-deps-el8” repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository… Failing package is: fping-4.2-2.el8.x86_64
GPG Keys are configured as: https://foreman.domain.com/katello/api/v2/repositories/4/gpg_key_content
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘yum clean packages’.
Error: GPG check FAILED
**

Success:

Foreman 3.10 and Proxy versions:

Foreman 3.10 and Proxy plugin versions:

Distribution and version:

Other relevant data:

GPG KEY for that repo is labeled

GPG KEY LABELED RPM-GPG-KEY-EPEL-8
upstream URL
https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFz3zvsBEADJOIIWllGudxnpvJnkxQz2CtoWI7godVnoclrdl83kVjqSQp+2
dgxuG5mUiADUfYHaRQzxKw8efuQnwxzU9kZ70ngCxtmbQWGmUmfSThiapOz00018
+eo5MFabd2vdiGo1y+51m2sRDpN8qdCaqXko65cyMuLXrojJHIuvRA/x7iqOrRfy
a8x3OxC4PEgl5pgDnP8pVK0lLYncDEQCN76D9ubhZQWhISF/zJI+e806V71hzfyL
/Mt3mQm/li+lRKU25Usk9dWaf4NH/wZHMIPAkVJ4uD4H/uS49wqWnyiTYGT7hUbi
ecF7crhLCmlRzvJR8mkRP6/4T/F3tNDPWZeDNEDVFUkTFHNU6/h2+O398MNY/fOh
yKaNK3nnE0g6QJ1dOH31lXHARlpFOtWt3VmZU0JnWLeYdvap4Eff9qTWZJhI7Cq0
Wm8DgLUpXgNlkmquvE7P2W5EAr2E5AqKQoDbfw/GiWdRvHWKeNGMRLnGI3QuoX3U
pAlXD7v13VdZxNydvpeypbf/AfRyrHRKhkUj3cU1pYkM3DNZE77C5JUe6/0nxbt4
ETUZBTgLgYJGP8c7PbkVnO6I/KgL1jw+7MW6Az8Ox+RXZLyGMVmbW/TMc8haJfKL
MoUo3TVk8nPiUhoOC0/kI7j9ilFrBxBU5dUtF4ITAWc8xnG6jJs/IsvRpQARAQAB
tChGZWRvcmEgRVBFTCAoOCkgPGVwZWxAZmVkb3JhcHJvamVjdC5vcmc+iQI4BBMB
AgAiBQJc9877AhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAh6kWrL4bW
oWagD/4xnLWws34GByVDQkjprk0fX7Iyhpm/U7BsIHKspHLL+Y46vAAGY/9vMvdE
0fcr9Ek2Zp7zE1RWmSCzzzUgTG6BFoTG1H4Fho/7Z8BXK/jybowXSZfqXnTOfhSF
alwDdwlSJvfYNV9MbyvbxN8qZRU1z7PEWZrIzFDDToFRk0R71zHpnPTNIJ5/YXTw
NqU9OxII8hMQj4ufF11040AJQZ7br3rzerlyBOB+Jd1zSPVrAPpeMyJppWFHSDAI
WK6x+am13VIInXtqB/Cz4GBHLFK5d2/IYspVw47Solj8jiFEtnAq6+1Aq5WH3iB4
bE2e6z00DSF93frwOyWN7WmPIoc2QsNRJhgfJC+isGQAwwq8xAbHEBeuyMG8GZjz
xohg0H4bOSEujVLTjH1xbAG4DnhWO/1VXLX+LXELycO8ZQTcjj/4AQKuo4wvMPrv
9A169oETG+VwQlNd74VBPGCvhnzwGXNbTK/KH1+WRH0YSb+41flB3NKhMSU6dGI0
SGtIxDSHhVVNmx2/6XiT9U/znrZsG5Kw8nIbbFz+9MGUUWgJMsd1Zl9R8gz7V9fp
n7L7y5LhJ8HOCMsY/Z7/7HUs+t/A1MI4g7Q5g5UuSZdgi0zxukiWuCkLeAiAP4y7
zKK4OjJ644NDcWCHa36znwVmkz3ixL8Q0auR15Oqq2BjR/fyog==
=84m8
-----END PGP PUBLIC KEY BLOCK-----

2

I was able to get around the error

By disabling the nagios repo from the server which forced it to used the EPEL8 repo files instead

./Default_Organization_Nagios_NCPA_nagiosxi-deps-el8-18c7c07187c06217/packages/fping-4.2-2.el8.x86_64.rpm
./Default_Organization_EPEL_8_Everything_8_Everything_x86_64-ce45adfeed38110e/packages/nagios-plugins-fping-2.4.9-1.el8.x86_64.rpm

I checked the gpg key for nagios and its current.

this is the rpm
rpm -qpi Default_Organization_Nagios_NCPA_nagiosxi-deps-el8-18c7c07187c06217/packages/fping-4.2-2.el8.x86_64.rpm
warning: Default_Organization_Nagios_NCPA_nagiosxi-deps-el8-18c7c07187c06217/packages/fping-4.2-2.el8.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID c62934a0: NOKEY
Name : fping
Version : 4.2
Release : 2.el8
Architecture: x86_64
Install Date: (not installed)
Group : Unspecified
Size : 64875
License : BSD with advertising
Signature : RSA/SHA1, Thu 23 Jul 2020 03:52:09 PM PDT, Key ID 67a75c9bc62934a0
Source RPM : fping-4.2-2.el8.src.rpm
Build Date : Mon 19 Aug 2019 08:22:52 AM PDT
Build Host : buildvm-09.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://www.fping.org/
Bug URL : Bug List
Summary : Scriptable, parallelized ping-like utility
Description :
fping is a ping-like program which can determine the accessibility of
multiple hosts using ICMP echo requests. fping is designed for parallelized
monitoring of large numbers of systems, and is developed with ease of
use in scripting in mind.

3

I think I figured it out.

It was because the it was pulling from the nagios dependencies repo which has a separate gpg key which wasn’t in the nagios gpg key chain

Name Location Public GPG Key
Nagios Index of /nagios GPG-KEY-NAGIOS-V3
GPG-KEY-NAGIOS-V2
Nagios XI Dependencies Index of /nagiosxi-deps