Jenkins update issue | Public key for jenkins<-version> is not installed

[armin...@mmlab.de]

Hi Mailing List!

I get the following error since a couple of weeks. Platform is CentOS
Linux release 7.7.1908 (Core). Installed Jenkins is 2.232-1.1 .

If you do research with the error message, this is apparently an issue
that occurs every now and then.

Why does the maintainer always mess up with the GPG key?

How can it be fixed?

Thank you!

Best regards
Armin


The following updates will be applied on minibldjnk:
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
jenkins noarch 2.233-1.1 jenkins 63 M

Transaction Summary
================================================================================
Upgrade 1 Package
Updates failed to install with the following error message:
Public key for jenkins-2.233-1.1.noarch.rpm is not installed


__________ Information from mm-lab IT security __________The message was checked by ESET Mail Security.

[Mark Waite]

On Wednesday, April 22, 2020 at 7:01:40 AM UTC-6, armi wrote:

Hi Mailing List!

I get the following error since a couple of weeks. Platform is CentOS
Linux release 7.7.1908 (Core). Installed Jenkins is 2.232-1.1 .

If you do research with the error message, this is apparently an issue
that occurs every now and then.

Why does the maintainer always mess up with the GPG key?

How can it be fixed?

Thanks for asking and thanks for using Jenkins.  Jenkins 2.232 was the first Jenkins build from the Jenkins core release automation project.  It is the first change to the Jenkins GPG signing key in many, many years.

You can resolve it by following the directions on the Jenkins install page http://mirrors.jenkins-ci.org/redhat/ .  That page says:

WARNING: The gpg key use to sign our packages has been updated on 16th of April 2020, therefore you need to reimport it if you imported before this date.

The specific command you need to execute is:

 sudo rpm --import https://pkg.jenkins.io/redhat/jenkins.io.key

Thanks,

Mark Waite

[armin...@mmlab.de]

Am 22.04.2020 um 16:10 schrieb Mark Waite:
> sudo rpm --import https://pkg.jenkins.io/redhat/jenkins.io.key

Thank you @Mark! It worked with this import command for the moment.

It seems that the other keys I was trying to import previously were
wrong or deprecated:

https://jenkins-ci.org/redhat/jenkins-ci.org.key (deprecated key?)
https://pkg.jenkins.io/redhat-stable/jenkins.io.key (stable distribution?)

[Mark Waite]

On Wednesday, April 22, 2020 at 8:22:03 AM UTC-6, armi...@mmlab.de wrote:

Am 22.04.2020 um 16:10 schrieb Mark Waite:
> sudo rpm --import https://pkg.jenkins.io/redhat/jenkins.io.key

Thank you @Mark! It worked with this import command for the moment.

It seems that the other keys I was trying to import previously were
wrong or deprecated:

https://jenkins-ci.org/redhat/jenkins-ci.org.key (deprecated key?)
https://pkg.jenkins.io/redhat-stable/jenkins.io.key (stable distribution?)

Those keys are not wrong and they are not deprecated for their intended uses.  Those are the public keys that have been used to sign releases prior to Jenkins 2.232.  The current long term support (stable) release is 2.222.1, with the release of 2.222.2 coming soon.

When a stable release is delivered that requires the new key, the key in those locations will be updated.

Mark Waite