Repo (CDN) timeout issues in fresh install of MicroOS Aeon

Hi!

I’m running into a couple issues that appears be related to the CDN and repositories:

Here’s a brief summary:

  • Just installed a fresh installation of MicroOS (Aeon) on my machine, and on the first attempt, ran into a timeout issue in the installer.
  • Tried the install a second time, and it worked to completion.

Now, I was trying to install some drivers (NVIDIA), and during the transactional-update, it fails when refreshing repositories, with a timeout error.

If I follow the link to the *.gz file that fails in the console, it looks to be an OpenSUSE CDN URL, and in the browser it looks to be related to a comcast hosted url: opensusemirror.vod.comcast.com

Two questions:

  1. Does anyone know what’s going on with this? Is the CDN pointing me to an unreliable mirror?
  2. Is there a way to alter the repo URLS to simply use download.opensuse.org instead of the CDN (or other ways to solve the problem)?

Cheers!

Show full ouptut of

zypper ls -dr
zypper ls -dr
# | Alias                      | Name             | Enabled | GPG Check | Refresh | Priority | Type   | URI
--+----------------------------+------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------
1 | NVIDIA                     | NVIDIA           | Yes     | ----      | Yes     |          | ris    | dir:/usr/share/zypp/local/service/NVIDIA
  | NVIDIA:repo-non-free       | repo-non-free    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.nvidia.com/opensuse/tumbleweed/
2 | openSUSE                   | openSUSE         | Yes     | ----      | Yes     |          | ris    | dir:/usr/share/zypp/local/service/openSUSE
  | openSUSE:repo-non-oss      | repo-non-oss     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed//repo/non-oss
  | openSUSE:repo-openh264     | repo-openh264    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed
  | openSUSE:repo-oss          | repo-oss         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed//repo/oss
- | openSUSE:repo-oss-debug    | repo-oss-debug   | No      | ----      | ----    |   99     | NONE   | http://cdn.opensuse.org/debug/tumbleweed//repo/oss
- | openSUSE:repo-oss-source   | repo-oss-source  | No      | ----      | ----    |   99     | NONE   | http://cdn.opensuse.org/source/tumbleweed//repo/oss
  | openSUSE:update-tumbleweed | update-tumblew-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/update/tumbleweed/

I’ve traced the issue further - it looks like the CDN is redirecting me to a comcast mirror to which I get a timeout error:

$ tracepath opensusemirror.vod.comcast.com
 1?: [LOCALHOST]                      pmtu 1500
[...]
 9:  be-207-pe12.seattle.wa.ibone.comcast.net             38.309ms asymm  4 
10:  be-2312-cs03.seattle.wa.ibone.comcast.net            50.487ms asymm  5 
11:  be-1311-cr11.seattle.wa.ibone.comcast.net            38.168ms asymm  6 
12:  be-302-cr11.champa.co.ibone.comcast.net              70.533ms 
13:  be-1311-cs03.champa.co.ibone.comcast.net             68.596ms asymm 11 
14:  be-1314-cr14.champa.co.ibone.comcast.net             70.768ms asymm 10 
15:  be-301-cr13.1601milehigh.co.ibone.comcast.net        66.642ms asymm  9 
16:  be-1213-cs02.1601milehigh.co.ibone.comcast.net       67.371ms asymm  8 
17:  be-1311-cr11.1601milehigh.co.ibone.comcast.net       66.947ms asymm  7 
18:  be-304-cr21.350ecermak.il.ibone.comcast.net          69.950ms asymm  6 
19:  be-1321-cs23.350ecermak.il.ibone.comcast.net         67.510ms asymm  5 
20:  68.86.93.198                                         71.994ms asymm  6 
21:  et-0-0-25-sas01-d.northlake.il.ndcchgo.comcast.net   64.809ms asymm 11 
22:  lo0-t1s8024-d.northlake.il.ndcchgo.comcast.net       71.248ms asymm  8 
23:  lo0-t2s8005-d.northlake.il.ndcchgo.comcast.net       66.237ms asymm  9 
24:  lo0-t1s8001-d.northlake.il.ndcchgo.comcast.net       71.187ms asymm 10 
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply

I’ve also figured out that I can do something like:

# transactional-update --no-selfupdate shell

Then edit repos to allow me to run updates etc.

Not sure what’s going on with that mirror, but it’s pretty inconvenient when the CDN points that way!

Those are services that automatically update repository definitions. You got them because you have NVIDIA hardware which causes package openSUSE-repos-Leap-NVIDIA to be installed and this package also pulls in openSUSE-repos-Leap as dependency.

You can remove and lock both packages. Look in /etc/zypp/repos.d, you should have backup of previous repository definitions with suffix .rpmsave. Just restore them and edit as you like.

Recently there were multiple reports about CDN issues. Apparently it depends on geo location.

1 Like

Awesome, thanks!

The CDN is indeed geo-location dependent. I made a report regarding the CDN / mirror issues, and it’s not reproducible from certain geo-locations.

I can see in the tracepath output that the mirror isn’t reachable. I’ve reproduced this from two ISP connections - both end-up going through comcast in Seattle, and fail before reaching the mirror.

tracepath opensusemirror.vod.comcast.com -m 50 
 1?: [LOCALHOST]                      pmtu 1500
[...]
13:  be-205-pe12.seattle.wa.ibone.comcast.net             63.648ms asymm 17 
14:  be-2312-cs03.seattle.wa.ibone.comcast.net            70.453ms asymm 17 
15:  be-1311-cr11.seattle.wa.ibone.comcast.net            53.046ms asymm 17 
16:  be-302-cr11.champa.co.ibone.comcast.net              89.047ms asymm 22 
17:  be-1111-cs01.champa.co.ibone.comcast.net             85.376ms asymm 21 
18:  be-1313-cr13.champa.co.ibone.comcast.net             82.985ms asymm 20 
19:  be-301-cr13.1601milehigh.co.ibone.comcast.net       106.887ms 
20:  be-1414-cs04.1601milehigh.co.ibone.comcast.net      119.621ms asymm 18 
21:  be-1211-cr11.1601milehigh.co.ibone.comcast.net      255.689ms asymm 17 
22:  be-302-cr21.350ecermak.il.ibone.comcast.net          81.389ms asymm 17 
23:  be-1121-cs21.350ecermak.il.ibone.comcast.net         90.666ms asymm 17 
24:  ae33-ar02-d.northlake.il.ndcchgo.comcast.net         88.092ms asymm 17 
25:  et-0-0-25-sas04-d.northlake.il.ndcchgo.comcast.net  112.165ms asymm 18 
26:  lo0-t1s8016-d.northlake.il.ndcchgo.comcast.net       85.785ms asymm 18 
27:  lo0-t2s8015-d.northlake.il.ndcchgo.comcast.net       82.498ms asymm 19 
28:  lo0-t1s8009-d.northlake.il.ndcchgo.comcast.net      205.672ms asymm 20 
29:  no reply
30:  no reply
31:  no reply

It made me think a little bit about how when mirror selection is done locally, it allows your local computer to determine if that mirror is working. With a CDN, that is all masked through third-party infrastructure, so geo-specific connectivity issues can happen with little transparency to the end-user.

I was able to work around this, but if someone less familiar with Linux had this pop-up during the install process, they might stop attempting, or try a different distro.

It makes me think that after a certain number of timeout errors, it might still be prudent to have a fallback to a non-CDN mirror?

Anyway, OpenSUSE has been one of my favourite distros so far; I’m sure this will get sorted out - perhaps just some growing pains with the CDN being relatively new.

Cheers!