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.

Sign up for GitHub

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

Jump to bottom

[8.0] Migrate off of Fedora 39 container image #109822

Closed
mthalman opened this issue Nov 14, 2024 · 3 comments
Closed

[8.0] Migrate off of Fedora 39 container image #109822

mthalman opened this issue Nov 14, 2024 · 3 comments
Labels
area-Infrastructure

Comments

@mthalman
Copy link
Member

The Helix config in 8.0 references a Fedora 39 image that doesn't even exist (nor has it ever):

runtime/eng/pipelines/libraries/helix-queues-setup.yml

Line 65 in c1ae962

- (Fedora.39.Amd64.Open)Ubuntu.2204.Amd64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:fedora-39-helix

runtime/eng/pipelines/libraries/helix-queues-setup.yml

Line 71 in c1ae962

- (Fedora.39.Amd64.Open)Ubuntu.2204.amd64.open@mcr.microsoft.com/dotnet-buildtools/prereqs:fedora-39-helix

This should be investigated to see whether it even needs to be defined. Are there no jobs that run this environment?
@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 Nov 14, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Nov 14, 2024
@vcsjones vcsjones added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Nov 14, 2024
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

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

@akoeplinger
Copy link
Member

akoeplinger commented Nov 19, 2024 •
edited
Loading

We're using Fedora 38 in main so this looks like a mistake done as part of #101073

runtime/eng/pipelines/libraries/helix-queues-setup.yml

Line 61 in 6accd39

- (Fedora.38.Amd64.Open)Ubuntu.2204.Amd64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:fedora-38-helix

We're only running this in the runtime-extra-platforms pipeline and it indeed fails there in 8.0

akoeplinger added a commit that referenced this issue Nov 19, 2024
@akoeplinger
Use Fedora 38 helix queue instead of 39, like in main
2e00149 
This was introduced by #101073 but we the fedora-39-helix image doesn't exist and we're using 38 in main.

Fixes #109822
@akoeplinger akoeplinger mentioned this issue Nov 19, 2024
Merged
akoeplinger added a commit that referenced this issue Nov 19, 2024
@akoeplinger
Use Fedora 38 helix queue instead of 39, like in main (#109964)
315a900 
This was introduced by #101073 but we the fedora-39-helix image doesn't exist and we're using 38 in main.

Fixes #109822
@akoeplinger
Copy link
Member

Fixed with #109964

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Nov 19, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Dec 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Infrastructure
Projects
Runtime Infra
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vcsjones @akoeplinger @mthalman