Comment 4 for bug 1862700

I've tried all the way down until 201906. 'vagrant box add' reported the same error for each one of them. Although 20200210 file size looks strange indeed, I don't know if this is the case for other images.

For some of them I've downloaded manually using the same commands as 'vagrant box add --debug ubuntu/bionic64' does. The commands bellow are for 20200206, which appears to be good.

$ $VAGRANTPATH/embedded/bin/curl -q --fail --location --max-redirs 10 --verbose --user-agent 'Vagrant/2.2.7 (+https://www.vagrantup.com; ruby2.4.9)' --continue-at '-' --output $HOME/.vagrant.d/tmp/boxtest http://cloud-images.ubuntu.com/bionic/20200206/bionic-server-cloudimg-amd64-vagrant.box
$ mkdir $HOME/.vagrant.d/tmp/boxtestout
$ $VAGRANTPATH/embedded/bin/bsdtar --no-same-owner --no-same-permissions -v -x -m -s "|\\\\|/|" -C $HOME/.vagrant.d/tmp/boxtestout -f $HOME/.vagrant.d/tmp/boxtest
x box.ovf
x Vagrantfile
x metadata.json
x ubuntu-bionic-18.04-cloudimg.mf
x ubuntu-bionic-18.04-cloudimg.vmdk: Truncated tar archive
bsdtar: Error exit delayed from previous errors.

Even GNU tar complains:

$ tar -xvf bionic-server-cloudimg-amd64-vagrant.box -C out/
box.ovf
Vagrantfile
metadata.json
ubuntu-bionic-18.04-cloudimg.mf
ubuntu-bionic-18.04-cloudimg.vmdk
tar: Unexpected EOF in archive
tar: rmtlseek not stopped at a record boundary
tar: Error is not recoverable: exiting now

Yes, ubuntu/bionic64 20200210. But I think there's more.