So, first off thank you for making such an amazing product! I utilize vagrant in my daily workflow as a pentester to ensure I have a clean environment per pentest (video with me talking about that here). So really appreciate it!
So, getting to my issue. I follow the HashiCorp Engineering Blog, and one of the posts talked about deb/rpm packaging for different HashiCorp (HC) products (which is awesome btw, thank you!).
Unfortunately though, I am having issues with vagrant installing properly because of a mismatched checksum error. Specifically this is the error:
root@packer-build-box:~# apt install vagrant
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
vagrant
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 43.1 MB of archives.
After this operation, 126 MB of additional disk space will be used.
Get:1 https://apt.releases.hashicorp.com focal/main amd64 vagrant amd64 2.2.10 [43.1 MB]
Err:1 https://apt.releases.hashicorp.com focal/main amd64 vagrant amd64 2.2.10
Hash Sum mismatch
Hashes of expected file:
- SHA256:edec76069f5805bfa70b3e46bc54f2cd3e64c9bca9d198d8d0e5da27c4121778
- SHA1:c4b54427617d428f8bfee819adde7a113a444833 [weak]
- Filesize:43089412 [weak]
Hashes of received file:
- SHA256:4390d75a6bcd05207282aeb4e2fa1a086c5b14d4d58ba4772ae76cb02bc3e7d7
- SHA1:b655fb36102fb4f3e8d3239fc38c72c1f60cf8b5 [weak]
- Filesize:43089412 [weak]
Last modification reported: Tue, 25 Aug 2020 19:57:13 +0000
Fetched 43.1 MB in 0s (99.6 MB/s)
E: Failed to fetch https://apt.releases.hashicorp.com/pool/amd64/main/vagrant_2.2.10_amd64.deb Hash Sum mismatch
Hashes of expected file:
- SHA256:edec76069f5805bfa70b3e46bc54f2cd3e64c9bca9d198d8d0e5da27c4121778
- SHA1:c4b54427617d428f8bfee819adde7a113a444833 [weak]
- Filesize:43089412 [weak]
Hashes of received file:
- SHA256:4390d75a6bcd05207282aeb4e2fa1a086c5b14d4d58ba4772ae76cb02bc3e7d7
- SHA1:b655fb36102fb4f3e8d3239fc38c72c1f60cf8b5 [weak]
- Filesize:43089412 [weak]
Last modification reported: Tue, 25 Aug 2020 19:57:13 +0000
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I ran the recommended command at the bottom apt-get update --fix-missing
to make sure it wasn’t a cache thing (like it was recommending), but still got the same result.
I am guessing it something to do with the checksum in the repos. This is all the info I can think to enumerate from my end:
root@packer-build-box:~# apt info vagrant
Package: vagrant
Version: 2.2.10
Priority: extra
Section: default
Maintainer: HashiCorp <support@hashicorp.com>
Installed-Size: 126 MB
Homepage: https://www.vagrantup.com/
License: MIT
Vendor: HashiCorp
Download-Size: 43.1 MB
APT-Sources: https://apt.releases.hashicorp.com focal/main amd64 Packages
Description: Vagrant is a tool for building and distributing development environments.
root@packer-build-box:~# apt-cache show vagrant
Package: vagrant
Version: 2.2.10
License: MIT
Vendor: HashiCorp
Architecture: amd64
Maintainer: HashiCorp <support@hashicorp.com>
Installed-Size: 122973
Section: default
Priority: extra
Homepage: https://www.vagrantup.com/
Description: Vagrant is a tool for building and distributing development environments.
Description-md5: 2bef0c3fc60e83db8996e2e5a37d9365
Filename: pool/amd64/main/vagrant_2.2.10_amd64.deb
SHA1: c4b54427617d428f8bfee819adde7a113a444833
SHA256: edec76069f5805bfa70b3e46bc54f2cd3e64c9bca9d198d8d0e5da27c4121778
Size: 43089412
Package: vagrant
Version: 2.2.9
License: MIT
Vendor: HashiCorp
Architecture: amd64
Maintainer: HashiCorp <support@hashicorp.com>
Installed-Size: 122753
Section: default
Priority: extra
Homepage: https://www.vagrantup.com/
Description: Vagrant is a tool for building and distributing development environments.
Description-md5: 2bef0c3fc60e83db8996e2e5a37d9365
Filename: pool/amd64/main/vagrant_2.2.9_amd64.deb
SHA1: 7dfd86f4733c3b6812a1a244ed9bf3b230d679d2
SHA256: 4b66c30b39278179ccc3f65e734d65f3a5612614e53e94cdfc80cf6f5075f295
Size: 42978788
I use it in my ansible role here: https://github.com/elreydetoda/ansible_virtualization/blob/master/roles/vagrant/tasks/install_Debian.yml ( to give context as to how I was using it ), but then ssh’ed into the machine during my CircleCI build (don’t know if you can see the logs or not, but figured I would provide the link in case you could).
For now I can just use this other role (which installs directly from your hosted web page) to install, but I figured I would bring it up so someone could address it.
Again, thank you for this amazing product and let me know if I can help with trying to figure out a solution to this issue.