Old Vagrant Images Redirect to Current Image

[Eric Blom]

It appears that all old vagrant images are not accessible because they redirect to the current image. I discovered this while looking into bug 1862700. In that case (ubuntu/bionic) all boxes fail because the current box is corrupt. For ubuntu/trusty64 both versions appear to work, but the resulting VMDK images have the same MD5 sum.

vagrant init ubuntu/trusty64 --box-version 20190514.0.0; vagrant up
vagrant init ubuntu/trusty64 --box-version 20190429.0.1; vagrant up

% md5 20190429.0.1/virtualbox/box-disk1.vmdk
MD5 (20190429.0.1/virtualbox/box-disk1.vmdk) = b8fc4ba0e39e33d119854e1e4bc8df0b <-- same
% md5 20190514.0.0/virtualbox/box-disk1.vmdk
MD5 (20190514.0.0/virtualbox/box-disk1.vmdk) = b8fc4ba0e39e33d119854e1e4bc8df0b <-- same
% pwd
~/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64
%

The URL displayed by Vagrant is correct in all cases. However, the URL results in a redirect that goes to /current.

ubuntu/bionic64
===============
vagrant init ubuntu/bionic64 --box-version 20200206.0.0
https://vagrantcloud.com/ubuntu/boxes/bionic64/versions/20200206.0.0/providers/virtualbox.box
https://app.vagrantup.com/ubuntu/boxes/bionic64/versions/20200206.0.0/providers/virtualbox.box
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64-vagrant.box
MD5 (bionic-server-cloudimg-amd64-vagrant.box) = 94d871536d24e3ad6ca6abceb91905e1

vagrant init ubuntu/bionic64 --box-version 20200210.0.0
https://vagrantcloud.com/ubuntu/boxes/bionic64/versions/20200210.0.0/providers/virtualbox.box
https://app.vagrantup.com/ubuntu/boxes/bionic64/versions/20200210.0.0/providers/virtualbox.box
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64-vagrant.box
MD5 (bionic-server-cloudimg-amd64-vagrant.box) = 94d871536d24e3ad6ca6abceb91905e1

ubuntu/trusty64
===============
vagrant init ubuntu/trusty64 --box-version 20190514.0.0
https://vagrantcloud.com/ubuntu/boxes/trusty64/versions/20190514.0.0/providers/virtualbox.box
https://app.vagrantup.com/ubuntu/boxes/trusty64/versions/20190514.0.0/providers/virtualbox.box
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box
MD5 (trusty-server-cloudimg-amd64-vagrant-disk1.box) = 79cf067a83f28cfb48390502be52884e

vagrant init ubuntu/trusty64 --box-version 20190429.0.1
https://vagrantcloud.com/ubuntu/boxes/trusty64/versions/20190429.0.1/providers/virtualbox.box
https://app.vagrantup.com/ubuntu/boxes/trusty64/versions/20190429.0.1/providers/virtualbox.box
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box
MD5 (trusty-server-cloudimg-amd64-vagrant-disk1.box) = 79cf067a83f28cfb48390502be52884els

[Pat Viafore (patviafore)]

Hello Eric,

Thanks for filing this bug. I'm digging in to see just what went wrong. We've revoked the 20200210 corrupted image on https://app.vagrantup.com/ubuntu/boxes/bionic64, and I can confirm the errors that you're seeing. The 20200206 serial should be pointing to the 20200206 serial now, but older images may still point to current.

I will communicate back on this bug as we roll out fixes.

[Joshua Powers (powersj)]

Hi,

Going through old bugs to check in on status.

This appears to have been fixed and we have had multiple releases of vagrant images since this was reported. As such I am marking this as 'Fix Released'.

If you disagree, please do feel free to follow-up in the bug here with additional notes or logs. Thanks!