openSUSE admin

$ zypper lr --uri | grep update-sle
55 | openSUSE:update-sle | update-sle (15.5) | Yes | (r ) Yes | Yes | http://cdn.opensuse.org/update/leap/15.5/sle

Doing a "zypper -v up -d" results in the following. Deleting the contents of /var/cache/zypp does not help. This has been the case for at least 2 days now.
...
Checking whether to refresh metadata for update-sle (15.5)
Retrieving: repomd.xml ...............................................................................................................................................................................................................................................................[done (916 B/s)]
Retrieving: repomd.xml.asc ...........................................................................................................................................................................................................................................................[done (481 B/s)]
Retrieving: repomd.xml.key ...........................................................................................................................................................................................................................................................[done (924 B/s)]
Retrieving: repomd.xml .........................................................................................................................................................................................................................................................................[done]
Repository: update-sle (15.5)
Key Fingerprint: FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB 7C82
Key Name: SuSE Package Signing Key build@suse.de
Key Algorithm: RSA 2048
Key Created: Mon Sep 21 09:21:47 2020
Key Expires: Fri Sep 20 09:21:47 2024
Rpm Name: gpg-pubkey-39db7c82-5f68629b
Signature verification failed for file 'repomd.xml' from repository 'update-sle (15.5)'.

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: This file was modified after it has been signed. This may have been a malicious change,
so it might not be trustworthy anymore! You should not continue unless you know it's safe.

Note: This might be a transient issue if the server is in the midst of receiving new data. The
data file and its signature are two files which must fit together. In case the request hit the
server in the midst of updating them, the signature verification might fail. After a few
minutes, when the server has updated its data, it should work again.

Signature verification failed for file 'repomd.xml' from repository 'update-sle (15.5)'. Continue? yes/no: yes
Retrieving: 432eb59088755eb918c8b75cdb13917f37c7f11405d54afa8a673d235190f93d-deltainfo.xml.gz .............................................................................................................................................................................................[not found]
Retrieving repository 'update-sle (15.5)' metadata ............................................................................................................................................................................................................................................[error]
Repository 'update-sle (15.5)' is invalid.
[openSUSE:update-sle|http://cdn.opensuse.org/update/leap/15.5/sle] Valid metadata not found at specified URL
History:

• File './repodata/432eb59088755eb918c8b75cdb13917f37c7f11405d54afa8a673d235190f93d-deltainfo.xml.gz' not found on medium 'http://cdn.opensuse.org/update/leap/15.5/sle'
• Can't provide ./repodata/432eb59088755eb918c8b75cdb13917f37c7f11405d54afa8a673d235190f93d-deltainfo.xml.gz

Please check if the URIs defined for this repository are pointing to a valid repository.