Comment 1 for bug 1862700

Yes, it appears the *vagrant.box has an issue for 20200210. However, even when I try to add an older box using a command such as the following I get an error.

  vagrant init ubuntu/bionic64 \
    --box-version 20200121.0.0

I can see on the cloud-images.ubuntu.com server that the box file is suspiciously small.
* 20200210: 68 M
* 20200206: 307 M
* 20200204: 307 M
* 20200131: 307 M

Downloading an older box file and adding it manually works.
https://cloud-images.ubuntu.com/bionic/20200206/bionic-server-cloudimg-amd64-vagrant.box

2020
==> default: Adding box 'ubuntu/bionic64' (v20200115.0.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20200116.1.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20200130.1.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20200131.0.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20200206.0.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20200210.0.0) for provider: virtualbox -- Fail
2019
==> default: Adding box 'ubuntu/bionic64' (v20191113.0.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20190513.0.0) for provider: virtualbox -- Fail
==> default: Adding box 'ubuntu/bionic64' (v20190115.0.0) for provider: virtualbox -- Fail
2018
==> default: Adding box 'ubuntu/bionic64' (v20180426.0.0) for provider: virtualbox -- Fail