Connection timing out to azure repositary

[mohamed-shahid-afrid]

Description

When downloading few of the dependencies from Azure, getting the below error.
Err:1 http://azure.archive.ubuntu.com/ubuntu focal/universe amd64 libhiredis0.14 amd64 0.14.0-6
Could not connect to azure.archive.ubuntu.com:80 (20.106.104.242), connection timed out

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 18.04
• Ubuntu 20.04
• Ubuntu 22.04
• macOS 11
• macOS 12
• Windows Server 2019
• Windows Server 2022

Image version and build link

2.299.1
https://github.com/mohamed-shahid-afrid/ODIM/actions/runs/3908839713/jobs/6679837385

Is it regression?

https://github.com/mohamed-shahid-afrid/ODIM/actions/runs/3901619852

Expected behavior

the job to sucess while downloading all the dependencies

Actual behavior

not able to connect to azzure repositories

Repro steps

just re-run the failed jobs

[nulano]

Also mentioned in #6486 (comment) and #6677 (comment)

[mikhailkoliada]

Hello! We handed over that to azure support, but we do not control the mirror, network hiccups happen and nothing we can do about it :(

[frenck]

@mikhailkoliada I have to disagree a bit on that, and I, therefore, think this issue was closed prematurely.

GitHub could provide mitigation in routing, deploy runners that defaults to a working mirror, and similar solutions like that. Heck, even a workaround advise would be welcome.

I think it is too easy to say: Not our problem.

(Especially considering GitHub & Azure both owned by the same parent company).

@ Home Assistant this is causing serious problems with the intense flow of PRs we are currently receiving.

Please consider re-opening the issue (or one of the others) to at least provide a hub for people to gather on the problem and read up.

../Frenck

[frenck]

@ddobranic as per above, I think removing the triage label isn't appropriate.

[frenck]

@mikhailkoliada @ddobranic Please advise. Do you want me to open an new issue, that focusses on a solution/report from a GitHub perspective?

[salman01zp]

we are facing same issue.

[agdavydov81]

A few hours ago I had two jobs with the same problem.
Now one job is working fine with no effort on my part.
But the second job (with cross compilation) still can't fetch the required packages.
Looks like the only thing I can do is wait.

[levrik]

Actually I'm seeing the same issue from inside a docker build with the official archive.ubuntu.com.

I wonder what's the difference between the azure.archive. and this one.

[agdavydov81]

My jobs started working!
Hooray!