Foreman-client-release-3.11.2-1.el8.noarch.rpm signed with wrong GPG Key?

Support
1

Just updated to 3.11.2 on my proxies and it wanted to install foreman-client-release-3.11.2-1.el8.noarch.rpm.
Assumed it should be signed by this GPG key but seems it is not.
https://yum.theforeman.org/latest/RPM-GPG-KEY-foreman

DNF give me the error:
Error: GPG check FAILED

2 
rpm -qpi foreman-client-release-3.11.2-1.el8.noarch.rpm
Name        : foreman-client-release
Version     : 3.11.2
Release     : 1.el8
Architecture: noarch
Install Date: (not installed)
Group       : Applications/System
Size        : 2078
License     : GPLv3+
Signature   : RSA/SHA256, Wed 04 Sep 2024 06:58:52 PM UTC, Key ID cf5931890a1d89dc
Source RPM  : foreman-release-3.11.2-1.el8.src.rpm
Build Date  : Wed 04 Sep 2024 06:58:48 PM UTC
Build Host  : aws-x86-64-spot-prod-09266288-20240904-185230
Relocations : (not relocatable)
Vendor      : Fedora Copr - group @theforeman
URL         : https://theforeman.org
Summary     : Foreman client repositories meta-package
Description :
Defines yum repositories for Foreman clients.

Compared to:

rpm -qpi foreman-release-3.11.2-1.el8.noarch.rpm
Name        : foreman-release
Version     : 3.11.2
Release     : 1.el8
Architecture: noarch
Install Date: (not installed)
Group       : Applications/System
Size        : 2410
License     : GPLv3+
Signature   : RSA/SHA256, Wed 04 Sep 2024 07:52:31 PM UTC, Key ID 4e7082461790a6e6
Source RPM  : foreman-release-3.11.2-1.el8.src.rpm
Build Date  : Wed 04 Sep 2024 06:48:12 PM UTC
Build Host  : aws-x86-64-spot-prod-09266066-20240904-184314
Relocations : (not relocatable)
Vendor      : Fedora Copr - group @theforeman
URL         : https://theforeman.org
Summary     : Foreman repositories meta-package
Description :
Foreman repository contains open source and other distributable software for
distributions in RPM format. This package contains the repository configuration
for Yum.
3

Yeah, 4e7082461790a6e6 is the right key.

I’m looking into that.

4

Thanks!

Fixed the signature and added a check to our release scripts so that this doesn’t happen again:

5

Thanks, can confirm the package installs fine now.