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

Fedora Cloud Base Vagrant Image for Virtualbox Corrupted #160

Open
factuminc opened this issue May 6, 2020 · 2 comments
Open

Fedora Cloud Base Vagrant Image for Virtualbox Corrupted #160

factuminc opened this issue May 6, 2020 · 2 comments

Comments

@factuminc
Copy link

Downloaded https://download.fedoraproject.org/pub/fedora/linux/releases/32/Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-virtualbox.box

SHA256 checksum is the same as website after checking the file Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-virtualbox.box and box archive has no errors

The VMDK file within the box archive does not have the same SHA256 checksum as website. The checksum is B9232224AAB5E64D8BB2494239ECCCA1A84D5C6EA316998E79391866113F743C when I test the Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vmdk file locally (after extracted from box archive) rather than 39e8fe0062ae88714c5717ffa656f3c8ab1275a96d9802b742213faf17a6d502 (listed here: https://getfedora.org/static/checksums/Fedora-Cloud-32-1.6-x86_64-CHECKSUM).

Files downloaded were linked from https://alt.fedoraproject.org/cloud/. I have not yet discovered if there is another location to download vmdk file directly. In the meantime, it would be helpful if there another location to download the vmdks directly.

@factuminc
Copy link
Author

factuminc commented May 6, 2020

Additionally, I just noticed that a vmdk is available directly here (mirrors.rit.edu):

Index of /fedora/fedora/linux/releases/32/Cloud/x86_64/images/
Name↓	Last Modified:	Size:	Type:
../	 	-  	Directory
Fedora-Cloud-32-1.6-x86_64-CHECKSUM	2020-Apr-24 12:58:39	1.7K	application/octet-stream
Fedora-Cloud-Base-32-1.6.x86_64.qcow2	2020-Apr-22 18:36:57	288.8M	application/octet-stream
Fedora-Cloud-Base-32-1.6.x86_64.raw.xz	2020-Apr-22 18:37:10	196.0M	application/octet-stream
Fedora-Cloud-Base-32-1.6.x86_64.vmdk	2020-Apr-22 18:37:57	737.7M	application/octet-stream
Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-libvirt.box	2020-Apr-22 18:47:41	276.5M	application/octet-stream
Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-virtualbox.box	2020-Apr-22 18:48:05	289.3M	application/octet-stream

https://mirrors.rit.edu/fedora/fedora/linux/releases/32/Cloud/x86_64/images/Fedora-Cloud-Base-32-1.6.x86_64.vmdk

As a test I will also download the vmdk directly today and see if it has the same issue as the bundled vagrant vmdk in the box archive.

While writing this followup comment I noticed that the vmdk linked directly in this comment does have the same size as detailed the checksum:

Fedora-Cloud-Base-32-1.6.x86_64.vmdk: 773586944 bytes
SHA256 (Fedora-Cloud-Base-32-1.6.x86_64.vmdk) = 39e8fe0062ae88714c5717ffa656f3c8ab1275a96d9802b742213faf17a6d502

Downloading the vmdk directly does appear to at least be giving me a file with the same size listed within the image checksum

@factuminc
Copy link
Author

factuminc commented May 6, 2020

Quick update - direct VMDK download that is 737 M in size boots fine and has the correct checksum as expected/that is listed in Fedora-Cloud-32-1.6-x86_64-CHECKSUM. It would appear to me given the knowledge I have that the issue described occurs when building the vagrant box or perhaps with other failed step(s) leading up to gathering the components required with building the vagrant box.

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

No branches or pull requests

1 participant