Skip to content

CI (github-hosted): Switch to Fedora 41 #92

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

Merged
merged 1 commit into from
Jul 28, 2025
Merged

CI (github-hosted): Switch to Fedora 41 #92

merged 1 commit into from
Jul 28, 2025

Conversation

metalefty
Copy link
Member

Fedora 40 has reached its EoL and the image is no longer available.

Fedora 40 has reached its EoL and the image is no longer available.
@metalefty
Copy link
Member Author

See https://github.com/AlmaLinux/raspberry-pi/actions/runs/16512011186/job/46695604522#step:11:21

 ==> fedora: Box 'fedora/40-cloud-base' could not be found. Attempting to find and install...
    fedora: Box Provider: libvirt
    fedora: Box Version: >= 0
==> fedora: Loading metadata for box 'fedora/40-cloud-base'
    fedora: URL: https://vagrantcloud.com/api/v2/vagrant/fedora/40-cloud-base
==> fedora: Adding box 'fedora/40-cloud-base' (v40.20240414.0) for provider: libvirt (amd64)
    fedora: Downloading: https://vagrantcloud.com/fedora/boxes/40-cloud-base/versions/40.20240414.0/providers/libvirt/amd64/vagrant.box

Progress: 0% (Rate: 0*/s, Estimated time remaining: --:--:--)
Progress: 100% (Rate: 17/s, Estimated time remaining: --:--:--)
Progress: 100% (Rate: 11/s, Estimated time remaining: --:--:--)
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 404

@metalefty
Copy link
Member Author

@yuravk Any ideas to address the timeout issue in https://github.com/AlmaLinux/raspberry-pi/actions/runs/16516649831?

@yuravk
Copy link
Contributor

yuravk commented Jul 28, 2025

@yuravk Any ideas to address the timeout issue in https://github.com/AlmaLinux/raspberry-pi/actions/runs/16516649831?

I believe that happens when GitHub Runners are hight loaded. It worked for me around 12:00 EEST without any issue.

The hack could probably look like vagrant-libvirt/vagrant-libvirt#318

@andrewlukoshko andrewlukoshko merged commit b490e55 into master Jul 28, 2025
3 of 4 checks passed
@metalefty metalefty deleted the ci branch July 29, 2025 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants