Package: vagrant Version: 2.0.0+dfsg-1 Severity: wishlist User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic
Hi Antonio,
The vagrant 2.0.0+dfsg-1 package has been synced to Ubuntu for the bionic
release, but is not considered releasable here because its autopkgtests fail
on Ubuntu infrastructure. This is because the vagrant autopkgtest tries to
access network resources without using the http_proxy configured in the
environment:
Bringing machine 'default' up with 'libvirt' provider...
==> default: Box 'debian/artful64' could not be found. Attempting to find and in
stall...
default: Box Provider: libvirt
default: Box Version: >= 0
The box 'debian/artful64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://vagrantcloud.com/debian/artful64";]
Error: The requested URL returned error: 404 Not Found
+ cleanup
+ vagrant halt
==> default: Domain is not created. Please run `vagrant up` first.
+ vagrant destroy -f
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/v/vagrant/20171221_100053_c03fd@/log.gz)
Could these autopkgtests be adjusted to honor the http_proxy environment?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
