-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Wierd behavior. Checksum and version #13572
Labels
Comments
@tonypony220 Thanks for the quick report! I can confirm that we also affected and able to reproduce the reported issue on @AlmaLinux. Two cents:
$ vagrant init almalinux/10-kitten
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
[fog][WARNING] Unrecognized arguments: libvirt_ip_command
==> default: Box 'almalinux/10-kitten' could not be found. Attempting to find and install...
default: Box Provider: libvirt
default: Box Version: >= 0
==> default: Loading metadata for box 'almalinux/10-kitten'
default: URL: https://vagrantcloud.com/api/v2/vagrant/almalinux/10-kitten
==> default: Adding box 'almalinux/10-kitten' (v10.20241227.0) for provider: libvirt (amd64)
default: Downloading: https://vagrantcloud.com/almalinux/boxes/10-kitten/versions/10.20241227.0/providers/libvirt/amd64/vagrant.box
default: Calculating and comparing box checksum...
The checksum of the downloaded box did not match the expected
value. Please verify that you have the proper URL setup and that
you're downloading the proper file.
Expected: 6982a8eebe99473bfa5f1eb7e609449bd96d262a4ee39323868b1fd8924b603b
Received: ff735a9f17075145db8378f5884e35bd98f19a7ac828a1d9157021106a035809 |
FWIW also seeing the issue on fedora images in containerd CI. Same received hash which is weird to me. |
@austinvazquez Seems like it is working now. |
@LKHN true |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've no idea what is happening, it was fine on vagrant 4.2.0 and 4.2.2.
The only thing i see is that checksum is the same for diff boxes so i guess return from server is makes this go wild
ok delete version
ok, with qemu as provider
Debug output
Expected behavior
Actual behavior
Reproduction information
Vagrant version
Host operating system
Guest operating system
Steps to reproduce
Vagrantfile
# Copy-paste your Vagrantfile here. Remove any sensitive information such as passwords, authentication tokens, or email addresses.
The text was updated successfully, but these errors were encountered: