Plesk update fails: The GPG keys are already installed but they are not correct for this package

Created:

2016-11-16 12:49:15 UTC

Modified:

2017-04-24 12:10:45 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk update fails: The GPG keys are already installed but they are not correct for this package

Applicable to:

  • Plesk for Linux

Symptoms

A Parallels Plesk update/micrupodate installation fails with this error:

    warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID 4520afa9: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
Fatal error during packages installation: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
YumBaseError: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.

Cause

Atomic added a new key to their repository, so it is needed to update repository configuration.

Resolution

  1. Download a new key:

    rpm --import https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt
  2. Modify /etc/yum.repos.d/atomic.repo file with the following:

    gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.atomicorp.txt   
    file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt

    NOTE: If the previous command did not help, reconfigure atomic repository:

    # wget -q -O - http://www.atomicorp.com/installers/atomic | sh

    or disable GPG check for atomic repository in /etc/yum.repos.d/atomic.repo setting:

    gpgcheck=0
Have more questions? Submit a request
Please sign in to leave a comment.