agent: RPM : repomd.xml GPG signature verification error on Fedora 39
What’s wrong?
I cannot get updates on my Fedora 39 machine, dnf report problem with repomd.xml GPG signature
I had to disable GPG into /etc/yum.repos.d/grafana.repo to make dnf works again
```#repo_gpgcheck=1````
Steps to reproduce
Grafana repo installed on Fedora 38 or before, then upgrade to Fedora 39.
System information
Linux 6.5.11-300.fc39.x86_64
Software version
Grafana Agent 0.37
Configuration
Package installed while on Fedora 38, distro upgraded to Fedora 39
Logs
grafana 2.2 kB/s | 629 B 00:00
Error: Failed to download metadata for repo 'grafana': repomd.xml GPG signature verification error: Error during parsing OpenPGP packets: Parsing an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears to be created by a non-conformant OpenPGP implementation, see <https://github.com/rpm-software-management/rpm/issues/2351>.
because: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1101011 (6b)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 4
- Comments: 16 (4 by maintainers)
The work around is to install the .rpm file directly from the Grafana web site. As it is not signed, you won’t be able to verify the signature. This is safe as long as believe the grafana.com site has not been compromised.
https://grafana.com/grafana/download
The proper solution is to wait until Grafana use a new GPG key to sign the RPM file. We can only wait until this is done.
Also for me, after upgrading to Fedora 39 the grafana repo doesn’t work due to signature problems. The error message is slightly different:
I had an outdated repo file, but also after updating (see below) the problem persists.
Of course, the workaround disabling repo_gpgcheck works for me as well.
I can confirm now that setting
repo_gpgcheck=1in the repo file does not cause any errors on Fedora 39.Previously, I set it to
repo_gpgcheck=0to work around the error.Hi, we think we have fixed this. Could folks give a re-check please?
log from me trying in a fedora docker container
This used to error before, as people are saying in this issue. Now it works:
Any updates on this? Still seems to be a problem…
Yes, the problem is that the following signature is invalid: https://rpm.grafana.com/repodata/repomd.xml.asc
Whoever operates the repository needs to regenerate that file using a proper GPG implementation.
Assuming a proper
gpgversion is installed on the server,gpg --detach-sign --armor repodata/repomd.xmlwill do the trick.