Or, as I just recalled what I have read from Richard, that I should simply ignore the issue by not performing a manual update?

If I am right, I remember that MicroOS can perform update itself and I shouldn’t/don’t need to bother with that?
From: Charlie Chan <charlierrr@yahoo.com>
Sent: Sunday, April 16, 2023 2:48:42 PM
To: microos@lists.opensuse.org <microos@lists.opensuse.org>
Subject: Transactional-update error
 
Hi,

This happens for a while in my MicroOS system.  Every time when I perform "transactional-update dup" it shows the following message:

Repository 'openSUSE-Tumbleweed-Non-Oss' is invalid.
[repo-non-oss|http://download.opensuse.org/tumbleweed/repo/non-oss/] Valid metadata not found at specified URL
History:
 - Signature verification failed for repomd.xml
 - Can't provide /repodata/repomd.xml

Please check if the URIs defined for this repository are pointing to a valid repository.
Repository 'openSUSE-Tumbleweed-Oss' is invalid.
[repo-oss|http://download.opensuse.org/tumbleweed/repo/oss/] Valid metadata not found at specified URL
History:
 - Signature verification failed for repomd.xml
 - Can't provide /repodata/repomd.xml

It looks like the signature key for the mirror cannot be verified.  My current workaround is to perform signature verification every time before updating by either: (1) perform zypper -vvv ref -f; (2) Open the software package update UI in GNOME and click "trust the software repository". Both are a bit annoying.

Anything I can do to fix this issue? I believe there's something wrong in the config files of zypper. Thank you.

Regards,
Charlie