vagrant-proxyconf: vagrant-proxyconfig stopped working with Vagrant 2.2.13
I tested this with virtualbox and libvirt providers and the following Vagrantfile:
Vagrant.configure("2") do |config|
if Vagrant.has_plugin?("vagrant-proxyconf")
config.proxy.http = "http://x.x.x.x:8080/"
config.proxy.https = "http://x.x.x.x:8080/"
config.proxy.no_proxy = "192.168.0.118/24,::1,127.0.0.1/8,localhost"
end
config.vm.box = "generic/alpine38"
end
After upgrading to Vagrant 2.2.13, it stopped working.
E.g. http_proxy does not show up in the env anymore.
I would also expect the line
==> default: Configuring proxy environment variables...
on vagrant up.
I am using Arch linux.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 21
I can confirm, that this plugin (2.0.10) works with the latest vagrant. I tested the virtualbox as well as the libvirt provider.
Wow, just wow, this is awesome folks. Thank you so much for doing a little homework and providing details here. I cannot say thank you enough. The extra context has been very valuable so far.
Based off this upstream bug report
I did little further investigating and it does look like hashicorp has merged in a potential fix into their main branch (just a few hours ago) so I suspect we might see
Vagrant 2.2.14being released soon?!If we don’t see Vagrant 2.2.14 released in a few days, I’ll say we can discuss plan b, but I don’t want to distract anyone with that just yet.
There is an upstream report, which is likely related: https://github.com/hashicorp/vagrant/issues/12035 There seem to be many plugins broken right now. https://github.com/hashicorp/vagrant/commit/157db39938d36e977c1d9f71bc4b30b2b2bae8fe seems to fix it for some other plugins, but I have never build Vagrant, so I don’t know how to check, whether this also fixed this issue.
Good news folks:
2.2.14now.I’m going to call this officially ready to upgrade to 2.2.14, repair or reinstall your vagrant plugins as needed, you’ll only need too if Vagrant tells you too, after your upgrade.
I’ll commit these tests to the master. Since there are not vagrant-proxyconf changes I won’t be cutting a new release.
Here’s proof of passing unit tests.
$ be rspecAnd here’s my semi-automated acceptance tests:
$ be vagrant provision$ cat /etc/os-release$ cat /etc/environment$ cat /etc/default/docker$ id$ docker info$ git config -l@codylane: thanks for the gist to downgrade vagrant. Now with vagrant 2.2.10 proxyconf works as expected.
Also, thanks to you and @chucknelson for responding to this issue quite fast.
I think I know what the problem is but I’ll need more time to investigate.
But yeah, I’d still like to see
/etc/environmentfrom your VM as well asVAGRANT_LOG=debug vagrant provisionif your VM is already up and provisioned. ORVAGRANT_LOG=debug vagrant upif your VM is powered off or not created.The debug log is insanely huge, but it can be valuable. Before posting make sure it doesn’t contain any personal or sensitive data especially if you are behind a authenticated proxy.
I also confirmed as well during my lunch break that Vagrant 2.2.10 passed a couple integration tests and unit tests. I’m going to go ahead and update the Gemfile and Travis to use 2.2.10 since we know that this version works.
Sadly, I didn’t have the same luck testing vagrant-proxy config with Vagrant versions
2.2.11,2.2.12and2.2.13.I’ll need to spend more time with Vagrant’s Changelog to see what the heck they changed and or introduced. I’m growing a little wary about how hashicorp is releasing versions of Vagrant. It’s not the first time they have released without also implementing tests for the things they’ve changed. This has been problematic since vagrant 2.2.5. 2.2.9 was stable for a while.
It works on 2.2.10 and that is what I am using now. I can also post the contents of my /etc/environment tomorrow, when I am back in the office.