SLE15 SP3 client with Package Hub channel fails to upgrade to SLE15 SP5 when using SUSE Manager server

This document (000021367) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 4.3

Situation

Scheduled upgrade of SLE15 SP3 client to SLE15 SP5 via SUSE Manager webUI will eventually fail.

Product Migration task will stop and below trace can be seen in task Details:

...
Retrieving: perl-XML-Dumper-0.81-bp155.2.9.x86_64 (SUSE-PackageHub-15-SP5-Backports-Pool for x86_64 SAP) (269/1253), 25.7 KiB
Retrieving: perl-XML-Dumper-0.81-bp155.2.9.x86_64.rpm [.done]
perl-XML-Dumper-0.81-bp155.2.9.x86_64.rpm:
Header V3 RSA/SHA512 Signature, key ID 8a49eb0325db7ae0: NOKEY
V3 RSA/SHA512 Signature, key ID 8a49eb0325db7ae0: NOKEY

Looking for gpg key ID 25DB7AE0 in cache /var/cache/zypp/pubkeys.
Repository SUSE-PackageHub-15-SP5-Backports-Pool for x86_64 SAP does not define additional 'gpgkey=' URLs.
Abort, retry, ignore? [a/r/i] (a): a

Resolution

Import manually new Package Hub public gpg key from SUSE Manager, before upgrade of SP3 client.

On SUSE Manager server, new Package Hub gpg key can be found here:

/srv/www/htdocs/pub/packagehub-gpg-pubkey-8A49EB0325DB7AE0.key

Copy and import it on the affected client:

rpm --import packagehub-gpg-pubkey-8A49EB0325DB7AE0.key

Cause

SLE15 SP3 Package Hub uses outdated gpg key.

Additional Information

New Package Hub gpg key was added to SP4 and SP5 PackageHub-release packages. At this time SP3 was already out of general support, so the PackagHub-release package wasn't updated. While LTSS and SLES for SAP on SP3 are still in use, it is possible to hit this edge scenario with old Package Hub.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.