#1 Hyperscale repo GPG key should already be trusted
Opened by dcavalca. Modified

Running dnf update I get

Importing GPG key 0x2F86D6A1:
 Userid     : "Fedora EPEL (8) <epel@fedoraproject.org>"
 Fingerprint: 94E2 79EB 8D8F 25B2 1810 ADF1 21EA 45AB 2F86 D6A1
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8
Is this ok [y/N]: y
Key imported successfully
warning: /var/cache/dnf/centos-hyperscale-experimental-9ecf566256e419a5/packages/librepo-1.14.0-1.1.hsx.el8.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID eb3dac40: NOKEY
CentOS Stream 8 - Hyperscale Experimental       1.7 MB/s | 1.8 kB     00:00    
Importing GPG key 0xEB3DAC40:
 Userid     : "CentOS HyperScale SIG (https://wiki.centos.org/SpecialInterestGroup/Hyperscale) <security@centos.org>"
 Fingerprint: 9B04 530E 0ED6 ABC4 B2C3 58DD 2A01 FA2A EB3D AC40
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-HyperScale
Is this ok [y/N]: y
Key imported successfully

EPEL might be debatable, but our key should definitely be already imported and trusted in the spin.


This has been a long-running bug with how live spins are created, but I could probably see if we can get our key to be auto-trusted.

Metadata Update from @ngompa:
- Issue tagged with: Common

Metadata Update from @ngompa:
- Issue tagged with: c8s

Metadata