openSUSE admin

At a first glance, it seems to apply to 15.3 only - 15.2 updates seem fine. There must be something wrong with the scanning.

I'm seeing a variation of this with Tumbleweed stuff too:

ngompa@localhost ~> podman run --pull=always --rm -it registry.opensuse.org/opensuse/tumbleweed-dnf:latest
Trying to pull registry.opensuse.org/opensuse/tumbleweed-dnf:latest...
Getting image source signatures
Copying blob d5b4dbb06b4d [--------------------------------------] 0.0b / 0.0b
Copying config 4ea1effe77 done
Writing manifest to image destination
Storing signatures
9888a0cc6578:/ # dnf install python3-pytest
openSUSE Tumbleweed - OSS                       387  B/s | 622  B     00:01
Errors during downloading metadata for repository 'opensuse-tumbleweed-oss':
  - Status code: 404 for http://sjc.edge.kernel.org/opensuse/tumbleweed/repo/oss/repodata/0510dd5d95752e0f1a5714b0f4cd6ab5624d6d8cd363cc80a89e2e91854c8b6c-primary.xml.gz (IP: 147.75.69.165)
  - Status code: 404 for http://sjc.edge.kernel.org/opensuse/tumbleweed/repo/oss/repodata/197456b09a408749ba71e4e03c67a8b5ed091ea17e5f747b3972c0b09d5454fb-filelists.xml.gz (IP: 147.75.69.165)
Error: Failed to download metadata for repo 'opensuse-tumbleweed-oss': Yum repo downloading error: Downloading error(s): repodata/0510dd5d95752e0f1a5714b0f4cd6ab5624d6d8cd363cc80a89e2e91854c8b6c-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/197456b09a408749ba71e4e03c67a8b5ed091ea17e5f747b3972c0b09d5454fb-filelists.xml.gz - Cannot download, all mirrors were already tried without success
openSUSE Tumbleweed - Updates                    27 kB/s |  35 kB     00:01
Ignoring repositories: opensuse-tumbleweed-oss
allow_vendor_change is disabled. This option is currently not supported for downgrade and distro-sync commands
No match for argument: python3-pytest
Error: Unable to find a match: python3-pytest
9888a0cc6578:/ #

Hmm, seems the Tumbleweed environment is fine now, but Leap 15.3 remains broken. :(

According to the scanner, all is well.

However, I am wondering if this is really an internal issue at kernel.org - when we scan, we get the server "closest" to us, and all four edge.kernel.org mirrors report fine for 15.3. I'll ask the mirror admin.