/sbin/ifup: configuration for eth1 not found about icinga-vagrant HOT 4 CLOSED

That's coming from a workaround for Vagrant 1.8.5 - 1.9.1 which does not bring up the hostonly interface properly. Some users report to have a different naming schema for that interface, mine creates eth1.

      # workaround for Vagrant >1.8.4-1.9.1 not bringing up eth1 properly
      # https://github.com/mitchellh/vagrant/issues/8096
      app_config.vm.provision "shell", inline: "ifup eth1", run: "always"

You can modify such, or propose a better workaround. I don't have an idea how to properly fix that until Vagrant 1.9.2 is released which fixes that regression.

from icinga-vagrant.

Linking the issue: hashicorp/vagrant#8096

from icinga-vagrant.

I'll change the workaround to a generic tested fix, but still you should either downgrade to 1.8.4 or wait for 1.9.2 finally released. Or you'll manually apply the patch from hashicorp/vagrant#8096.

from icinga-vagrant.

https://github.com/mitchellh/vagrant/blob/v1.9.2/CHANGELOG.md

from icinga-vagrant.