core
core copied to clipboard
dotnet
dotnet CDN tracking issue
We are making important changes to the dotnet CND, due to azureedge.net domains no longer being supported/available, per https://github.com/dotnet/core/issues/9671.
The following are the tasks we intend to take on with target timelines. All of this is expected to evolve as we learn more.
Phase 1 (January):
- https://github.com/dotnet/install-scripts/issues/559
- https://github.com/dotnet/arcade/pull/15365
- https://github.com/dotnet/install-scripts/issues/558
- https://github.com/dotnet/install-scripts/issues/563
- https://github.com/dotnet/core/issues/9673
- https://github.com/dotnet/core/issues/9669
- https://github.com/dotnet/core/issues/9682
- https://github.com/dotnet/core/issues/9683
Phase 2 (February-March):
- https://github.com/dotnet/core/issues/9675
Phase 3 (April?):
- https://github.com/dotnet/core/issues/9676
Related:
- https://github.com/dotnet/core/issues/9677
- https://github.com/actions/setup-dotnet/issues/570
I don't know exactly what is going on the last few days, but we have a very hard time in reaching https://dot.net/v1/dotnet-install.sh from our Bitbucket pipelines.
+ curl -sSL https://dot.net/v1/dotnet-install.sh --output dotnet-install.sh
curl: (56) Recv failure: Connection timed out
Could this be part of this issue?
The .NET Website uses a different routing infrastructure before it gets to the new CDN urls - see https://github.com/dotnet/install-scripts/issues/582#issuecomment-2749567858 for more details. I though this was resolved already, but can investigate with the internal team that controls this infra for us again.
My monitoring is alerting that the redirection service is still having issues. I contacted the team again.
We have a backlog item to switch redirection services. We are planning on moving to Azure Front Door.