Old Vagrant Images Redirect to Current Image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
Pat Viafore |
Bug Description
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.
MD5 (20190429.
% md5 20190514.
MD5 (20190514.
% pwd
~/.vagrant.
%
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:/
https:/
https:/
MD5 (bionic-
vagrant init ubuntu/bionic64 --box-version 20200210.0.0
https:/
https:/
https:/
MD5 (bionic-
ubuntu/trusty64
===============
vagrant init ubuntu/trusty64 --box-version 20190514.0.0
https:/
https:/
https:/
MD5 (trusty-
vagrant init ubuntu/trusty64 --box-version 20190429.0.1
https:/
https:/
https:/
MD5 (trusty-
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.