Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azureedge.net URLs will stop working on 15 January and thus installing Edge will break #11244

Open
16 tasks done
Piedone opened this issue Dec 27, 2024 · 4 comments
Open
16 tasks done

Comments

@Piedone
Copy link

Piedone commented Dec 27, 2024

Description

This is really urgent so will need to be quick: see https://github.com/actions/setup-dotnet/releases/tag/v4.2.0 for the larger context, but the gist of it is that azureedge.net URLs will stop working on the 15th of January, possibly sooner. Thus, these scripts will stop working: https://github.com/search?q=repo%3Aactions%2Frunner-images%20azureedge.net&type=code

Platforms affected

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

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Image version and build link

No issue yet.

Is it regression?

Yes

Expected behavior

Edge install scripts can download Edge from msedgedriver.azureedge.net.

Actual behavior

Scripts will fail.

Repro steps

See above.

@RaviAkshintala
Copy link
Contributor

Hi @Piedone Thank you for bringing this issue to our attention. We are looking into this issue and will update you on this issue after investigating

@Piedone
Copy link
Author

Piedone commented Dec 27, 2024

Great, thanks!

@subir0071
Copy link
Contributor

Looking for alternative URL to download but was not able to.
Raised an issue with the edge-driver repository.
Awaited info..

@MatthewSteeples
Copy link

MatthewSteeples commented Jan 7, 2025

As crazy as it sounds, this isn't likely to be an issue. In addition to being used by Edgio, the azureedge.net domain is also used by Microsoft's Standard CDN and this is good until 2027. The only way you can tell which CDN provider is being used is by looking at the headers. The Microsoft one has an x-ms-request-id header, whereas the Edgio ones have x-edgio-request-id in them.

Simple eh? 😉 (and someone should have probably given the dotnet team that information too, as it looks like they're not even using Edgio...!)

Edit: would appear that information isn't quite correct. The x-ms-request-id header is coming from blob storage, not from the CDN. Doing some more digging.

Edit2: Best I can come up with is DNS checking, but I don't know how accurate that is. If you nslookup the domain and it resolves to v0cdn.net then it's Edgio, and t-msedge.net is Microsoft. I'm basing this on our own resources (but sadly we deleted the last of our Edgio resources last week so I only have some logs and screenshots to go on)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants