openSUSE admin

pjessen wrote:

History:

• [|] Error trying to read from 'https://cache.opensuse.net.br/tumbleweed/repo/oss/'
• Download (curl) error for 'https://cache.opensuse.net.br/tumbleweed/repo/oss/content': Error code: Unsupported protocol or redirect (location: http://downloadcontent-br.opensuse.org/tumbleweed/repo/oss/content) Error message: Redirect to protocol "http" not supported or disabled in libcurl

A downgrade from https to http is probably not permitted/supported. I would say some mirror misconfiguration.

Ah, OK. I think you're right. I forgot to post this:

$ curl -IL https://mirrorcache-br.opensuse.org/tumbleweed/repo/oss/content
HTTP/2 302                                                                                                                
server: nginx/1.21.5                                                                                                      
date: Wed, 14 Jun 2023 02:08:26 GMT
content-length: 0                                                                                                         
location: https://downloadcontent-br.opensuse.org/tumbleweed/repo/oss/content
cache-control: no-cache     

HTTP/1.1 404 Not Found
Server: nginx         
Date: Wed, 14 Jun 2023 02:08:32 GMT
Content-Type: text/html
Content-Length: 146
Connection: keep-alive
Vary: Accept-Encoding

$ curl -IL https://cache.opensuse.net.br/tumbleweed/iso/Changes.20230612.txt
HTTP/2 302           
date: Wed, 14 Jun 2023 02:14:54 GMT
content-length: 0
location: http://opensuse.redlibre.cl/tumbleweed/iso/Changes.20230612.txt
vary: Accept, COUNTRY
cache-control: no-cache
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=Kc8BFQSWIHx6IfdTHxDruLvCqKS4ii7D4FutTKqpQWGn
tnFWmzBFmxh4Di5yVzv2V%2BUnkgBCjpd2Lm%2BsRREzF7iZCr28IJGZpplaAYKkrpTpZC9nqoitl1i3gnaSdeExJL9PNMMe6PY%3D"}],"group":"cf-nel"
,"max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 7d6f0fff8ff51acd-GRU
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Wed, 14 Jun 2023 02:14:55 GMT
Server: Apache
Last-Modified: Tue, 13 Jun 2023 12:48:45 GMT
ETag: "9ea8-5fe02417a5173"
Accept-Ranges: bytes
Content-Length: 40616
Vary: Accept-Encoding
Content-Type: text/plain

So, cache.opensuse.net.br is redirecting HTTPS->HTTP. First I thought this was the third Brazilian MirrorCache, mirrorcache-br-3.opensuse.org (see https://status.opensuse.net.br/, Edgium). However, I can't find out on my own.

@avicenzi, you're more up to date when it comes to our mirroring infra, do you have any input?

That kind of solves the first part of the mystery. Now there's the phantom /tumbleweed/repo/oss/content that redirects to nowhere (404), from local MirrorCaches. And download-o-o gives 404 too.

@andriinikitin, do you have any insights one this?

Now there's the phantom /tumbleweed/repo/oss/content that redirects to nowhere (404), from local MirrorCaches. And download-o-o gives 404 too.

As does my mirror - I'm not sure what content is for, but maybe it wasn't published? FWIW, I don't see a file content in any of the leap/xx.x/repo/oss directories either.

pjessen wrote:

Now there's the phantom /tumbleweed/repo/oss/content that redirects to nowhere (404), from local MirrorCaches. And download-o-o gives 404 too.

As does my mirror - I'm not sure what content is for, but maybe it wasn't published? FWIW, I don't see a file content in any of the leap/xx.x/repo/oss directories either.

I kind of have the feeling I've seen it before, but I can't be sure either. The other mystery would be why some people are coming across with it.

luc14n0 wrote:

pjessen wrote:

Now there's the phantom /tumbleweed/repo/oss/content that redirects to nowhere (404), from local MirrorCaches. And download-o-o gives 404 too.

As does my mirror - I'm not sure what content is for, but maybe it wasn't published? FWIW, I don't see a file content in any of the leap/xx.x/repo/oss directories either.

I kind of have the feeling I've seen it before, but I can't be sure either. The other mystery would be why some people are coming across with it.

Yup, I agree - I think the question might be better asked on the factory list, there are no doubt some people there who are much more familiar with this process.

Yeah, I'm sure there are people on the Factory mailing list that must have some idea about this content. I'm gonna send an email there. And I'm gonna send an email to Tyna Host folks too, about that illegal HTTPS->HTTP redirection.

This is not an official URL and is not advised to be used.

cache.opensuse.net.br was created during our initial setup for testing purposes.

avicenzi wrote:

This is not an official URL and is not advised to be used.

cache.opensuse.net.br was created during our initial setup for testing purposes.

Interesting, people from US - more specifically from West coast (at least from California, where the latency to cache-o-n-br is low) - are being redirected to it. I suppose someone with admin privileges on mirrorcache-us can delete cache.opensuse.net.br, right?

I can't find cache.opensuse.net.br in the list of mirrors on mirrorcache-us.

luc14n0 wrote:

avicenzi wrote:

This is not an official URL and is not advised to be used.

cache.opensuse.net.br was created during our initial setup for testing purposes.

Interesting, people from US - more specifically from West coast (at least from California, where the latency to cache-o-n-br is low) - are being redirected to it. I suppose someone with admin privileges on mirrorcache-us can delete cache.opensuse.net.br, right?

cache.opensuse.net.br is not in the mirror us list.

cache.opensuse.net.br now points to download.opensuse.org and should behave properly or cause a redirect loop somewhere else.

Thanks Alex for the bandaid. We have to find this bleeding, though. It needs a bit of an investigation.

Alright, with the help of Patrick, from the community, we found out it's mirrorsorcer that introduced cache.opensuse.net.br without knowing it's not an official redirector.

luc14n0 wrote:

Yeah, I'm sure there are people on the Factory mailing list that must have some idea about this content.
I'm gonna send an email there. And I'm gonna send an email to Tyna Host folks too, about that illegal HTTPS->HTTP redirection.

The redirection might be fine, it could be us listing an unsupported https url. (I guess I am a bit late with that comment).

pjessen wrote:

luc14n0 wrote:

Yeah, I'm sure there are people on the Factory mailing list that must have some idea about this content.
I'm gonna send an email there. And I'm gonna send an email to Tyna Host folks too, about that illegal HTTPS->HTTP redirection.

The redirection might be fine, it could be us listing an unsupported https url. (I guess I am a bit late with that comment).

In any case, I consider the cache.opensuse.net.br mystery as solved. That server shouldn't be used by openSUSE users - its purpose was for testing -, and mirrorsorcerer was mistakenly using it to enhance users' experience.

I realized something when giving a new look at the error output, and after reading:

 - [|] Error trying to read from 'https://cache.opensuse.net.br/tumbleweed/repo/oss/'
 - Download (curl) error for 'https://cache.opensuse.net.br/tumbleweed/repo/oss/content':

I had the thought: Zypper/libzypp must be expecting /content. And a quick grep under libzypp's source tree gave me quite some results, like the comment [1]:

/** Repository content data (from /content file).
 * File and Checksum definitions required by Downloader and Parser.
 * (Do not confuse with NU's repoindex.xml)
 */

I'm going to ask around the libzypp GH repo.

1. https://github.com/openSUSE/libzypp/blob/e72ee3baa2c038792d72a01f7ccd4c7d4c5bb188/zypp/parser/susetags/RepoIndex.h#L44

For reference: https://github.com/openSUSE/libzypp/issues/468