Ad Widget

Collapse

GPG Key issue with 6.0.43 agent update?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • suny sm
    Junior Member
    • Dec 2025
    • 1

    #1

    GPG Key issue with 6.0.43 agent update?

    Never had an issue with update from the repository, these are well maintained servers with all the latest updates.

    dnf shows current installed version is 6.0.42-release1.el8

    Seeing across all our servers (OEL8). dnf clean did not resolve, nor did I anticipate it would.

    I see nothing in release notes indicating a repository key change in 6.0.43. The key referenced matches the (2016 dated) key in the repo.

    We are very security conscious and our perception is the 6.0.43 package was not properly signed, corrupt or not genuine.

    Wondering if others can shed light on this.


    $ sudo dnf update
    This system is receiving updates from Unbreakable Linux Network or Spacewalk.
    Last metadata expiration check: 0:27:21 ago on Wed 17 Dec 2025 10:54:49 AM EST.
    Dependencies resolved.
    ================================================== ================================================== ===========================================
    Package Architecture Version Repository Size
    ================================================== ================================================== ===========================================
    Upgrading:
    zabbix-agent x86_64 6.0.43-release1.el8 zabbix 588 k

    Transaction Summary
    ================================================== ================================================== ===========================================
    Upgrade 1 Package

    Total download size: 588 k
    Is this ok [y/N]: y
    Downloading Packages:
    zabbix-agent-6.0.43-release1.el8.x86_64.rpm 833 kB/s | 588 kB 00:00
    -----------------------------------------------------------------------------------------------------------------------------------------------
    Total 829 kB/s | 588 kB 00:00
    Zabbix Official Repository - x86_64 1.6 MB/s | 1.7 kB 00:00
    GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 (0xA14FE591) is already installed
    The GPG keys listed for the "Zabbix Official Repository - x86_64" 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: zabbix-agent-6.0.43-release1.el8.x86_64
    GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
    The downloaded packages were saved in cache until the next successful transaction.
    You can remove cached packages by executing 'dnf clean packages'.
    Error: GPG check FAILED
  • k0ka
    Junior Member
    • Dec 2025
    • 1

    #2
    Have the same issue. Also on EL8 (Rocky). Didn't find the root cause so decided to postpone that update to make sure it's genuine release.

    Comment

    • Neal.H
      Junior Member
      • Jun 2020
      • 11

      #3
      Not able to shed any light on this beyond confirming I am also seeing the same issue when installing Zabbix Agent 6.0.43 on a fully patched XCP-NG 8.3 server. Zabbix Agent 6.0.42 installed without issues on another identical setup a few weeks ago, and I can still install that version if I also specify its dependency versions eg:

      Code:
      yum install zabbix-agent2-6.0.42 zabbix-agent2-plugin-postgresql-6.0.42 zabbix-agent2-plugin-mongodb-6.0.42

      Comment

      • itas
        Junior Member
        • Dec 2025
        • 1

        #4
        Same here. It also happens on EL7, which is out of support, but on extended support from Red Hat.

        Comment

        • Tom-in-NM
          Junior Member
          • Jan 2023
          • 1

          #5
          Confirmed, still happening with RHEL8 and Oracle Linux 8

          rpm -qi zabbix-agent-6.0.43-release1.el8.x86_64.rpm
          warning: zabbix-agent-6.0.43-release1.el8.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID b5333005: NOKEY
          Name : zabbix-agent
          Version : 6.0.43
          Release : release1.el8
          Architecture: x86_64
          Install Date: (not installed)
          Group : Applications/Internet
          Size : 2295920
          License : GPLv2+
          Signature : RSA/SHA512, Tue 16 Dec 2025 05:42:23 PM UTC, Key ID d913219ab5333005
          Source RPM : zabbix-6.0.43-release1.el8.src.rpm
          Build Date : Tue 16 Dec 2025 05:39:54 PM UTC
          Build Host : builds-x86
          Relocations : (not relocatable)
          URL : http://www.zabbix.com/
          Summary : Zabbix agent
          Description :
          Old implementation of zabbix agent.
          To be installed on monitored systems.

          Comment

          • vmorel
            Junior Member
            • Aug 2024
            • 1

            #6
            Hello!
            Same error here on Oracle Linux 8. No problem with server using Oracle Linux 9...

            Comment

            • YBusherb
              Junior Member
              • Jul 2022
              • 3

              #7
              Same issue here
              The GPG listed here seems to not have changed: https://repo.zabbix.com/
              Is the package wrongly signed?

              Comment

              • n1am
                Junior Member
                • May 2017
                • 4

                #8
                I solved on CentOS 7 with:
                Code:
                curl https://repo.zabbix.com/RPM-GPG-KEY-ZABBIX-A14FE591 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
                curl https://repo.zabbix.com/RPM-GPG-KEY-ZABBIX-B5333005 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-B5333005
                sed -i 's/RPM-GPG-KEY-ZABBIX-A14FE591/RPM-GPG-KEY-ZABBIX-B5333005/g' /etc/yum.repos.d/zabbix.repo

                Comment

                • YBusherb
                  Junior Member
                  • Jul 2022
                  • 3

                  #9
                  Just found the issue: https://support.zabbix.com/browse/ZBX-27327
                  new packages were released 8 hours ago (release2)
                  should fix the issue

                  Comment

                  Working...