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

Missing centos-stream9 runtime assets #102344

Closed
MiYanni opened this issue May 16, 2024 · 6 comments · Fixed by #103708
Closed

Missing centos-stream9 runtime assets #102344

MiYanni opened this issue May 16, 2024 · 6 comments · Fixed by #103708
Assignees

Comments

@MiYanni
Copy link
Member

MiYanni commented May 16, 2024

Description

Summary

In transitioning the dotnet/installer repo into dotnet/sdk, the build uses some Linux containers. One of them is centos-stream9. However, the build does not succeed to download some runtime assets specific to this container.

Here are some example URLs it was looking for:

https://dotnetcli.blob.core.windows.net/dotnet/Runtime/9.0.0-preview.4.24251.2/dotnet-runtime-deps-9.0.0-preview.4.24251.2-centos.9-x64.rpm
 
https://dotnetbuilds.blob.core.windows.net/public/Runtime/9.0.0-preview.4.24251.2/dotnet-runtime-deps-9.0.0-preview.4.24251.2-centos.9-x64.rpm
 
https://dotnetbuilds.blob.core.windows.net/internal/Runtime/9.0.0-preview.4.24251.2/dotnet-runtime-deps-9.0.0-preview.4.24251.2-centos.9-x64.rpm

However, if you change the ending from .9-x64.rpm to .8-x64.rpm, the links are valid and able to download the assets. This leads me to believe the assets are not being published for centos-stream9 but are still being published for centos-stream8.

Reproduction Steps

Try downloading the asset from any of these links:

Expected behavior

The assets are able to be downloaded.

Actual behavior

They will fail to download/don't exist.

Regression?

No response

Known Workarounds

I've told the build to use centos-stream8 for the time being since those assets exist.

Configuration

This was specific to building the dotnet/sdk repo in AzDO on the centos-stream9 Linux container.

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 16, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label May 16, 2024
@NikolaMilosavljevic NikolaMilosavljevic self-assigned this May 21, 2024
@ericstj ericstj removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 21, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@NikolaMilosavljevic
Copy link
Member

CI legs for CentOS-Stream9 are missing in runtime repo.

@akoeplinger
Copy link
Member

akoeplinger commented Jun 19, 2024

We presumably need to update https://github.com/dotnet/runtime/blob/main/src/installer/pkg/sfx/installers/dotnet-runtime-deps/dotnet-runtime-deps-centos.8.proj

@jkoritzinsky I see you updated these last year in #84805, do you know who owns these packages?

@akoeplinger
Copy link
Member

Also ties in with #103379

@jkoritzinsky
Copy link
Member

@NikolaMilosavljevic and I generally do the work for them. Officially, @NikolaMilosavljevic's team owns them.

I can update the packages again (just CentOS Stream this time because RHEL/Oracle Linux 8 are still supported in .NET 9)

@MiYanni
Copy link
Member Author

MiYanni commented Jun 19, 2024

@jkoritzinsky Can you let me know when the runtime change flows into the SDK? I can make a PR for the SDK after that to update the container there.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Jun 19, 2024
akoeplinger added a commit to dotnet/sdk that referenced this issue Jun 20, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants