🐛RPM repository on pkg.cloudlfare.com using old key

[michel-zimmer]

Describe the bug
I'm unable to properly configure the RPM repository. The error message is File 'repomd.xml' from repository 'cloudflare-stable' is signed with an unknown key '254B391D8CACCBF8'..

To Reproduce
Steps to reproduce the behavior:
Configure RPM repository either manually or using the repo file https://pkg.cloudflare.com/cloudflared.repo like this for example:

zypper addrepo --repo https://pkg.cloudflare.com/cloudflared.repo
…
Repository 'cloudflared-stable' successfully added

But when actually accessing the repo like this for example:

zypper refresh
…
Looking for gpg keys in repository cloudflared-stable.
  gpgkey=https://pkg.cloudflare.com/cloudflare-ascii-pubkey.gpg
Looking for gpg keys in repository cloudflared-stable.
  gpgkey=https://pkg.cloudflare.com/cloudflare-ascii-pubkey.gpg
Warning: File 'repomd.xml' from repository 'cloudflared-stable' is signed with an unknown key '254B391D8CACCBF8'.

    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: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the
    whole repo.

    Warning: We can't verify that no one meddled with this file, so it might not be trustworthy
    anymore! You should not continue unless you know it's safe.

File 'repomd.xml' from repository 'cloudflared-stable' is signed with an unknown key '254B391D8CACCBF8'.
Continue? [yes/no] (no): 
…

Expected behavior
I expect the signing key referenced in the repo file to match the key used for the repository.

Environment and versions

• OS: SLES
• Architecture: amd64
• Version: 15 SP7

Logs and errors
-If applicable, add logs or errors to help explain your problem.-

Additional context
I have seen the warning message on https://pkg.cloudflare.com/index.html and I have seen that the key got properly revoked https://keyserver.ubuntu.com/pks/lookup?search=254B391D8CACCBF8&fingerprint=on&op=index, but I still don't know how to solve this correctly. To me it appears as if the new key is in place for download and so on, but the repo is still using the old key.