Suse Manager Server rejects to trust the gpg key when channel synchronization is scheduled by default setting

SUSE Linux Enterprise Server 15 SP5
SUSE Manager 4.3
Red Hat Enterprise Linux 9

SUSE Manager server rejects the gpg key when channel synchronization is scheduled by the default setting:

susemanager:~ # /usr/bin/spacewalk-repo-sync --channel el9-manager-tools-pool-x86_64 --type yum
10:00:38 ======================================
10:00:38 | Channel: el9-manager-tools-pool-x86_64
10:00:38 ======================================
10:00:38 Sync of channel started.

New repository or package signing key received:

Repository: el9-manager-tools-pool-x86_64
Key Fingerprint: CCB5 7F6E 2FA5 D41B 256E 02B8 97A6 36DB 0BAD 8ECC
Key Name: SUSE product addon <build-addon@suse.de>
Key Algorithm: RSA 4096
Key Created: Wed Sep 21 14:11:19 2022
Key Expires: Sun Sep 20 14:11:19 2026
Rpm Name: gpg-pubkey-0bad8ecc-632aff67

Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.

Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): r

Rebuild the database where the keys are stored:
# rpmdb -vv --rebuilddb --dbpath=/var/lib/spacewalk/reposync/root/var/lib/rpm

Synchronize the affected channels again:
ex. # spacewalk-repo-sync -c el9-manager-tools-pool-x86_64
ex. # spacewalk-repo-sync -c suse-packagehub-15-sp5-backports-pool-x86_64

Possible database corruption.