ARPCHECK=no /sbin/ifup eth1 2> /dev/null

[lmayorga1980]

Vagrant: 1.6.3
OS: CentOS 7.0

Full Debug Log

https://gist.github.com/lmayorga1980/c138c47c13d8f53431d8

I had to follow some directions in order to fix ti by removing the following file but it did not work...

rm -rf /etc/udev/rules.d/70-persistent-net.rules

    centos.vm.box      = 'lmayorga1980/centos7-puppet'
    centos.vm.hostname = 'cmserver'
    centos.vm.network   :private_network, ip: '10.11.0.100'
    centos.vm.network   "forwarded_port", guest: 4440, host: 4440, auto_correct: true

[tricktrap]

Vagrant: 1.6.3
OS: CentOS 7.0

I've had this issue pop up for me as well (similar debug log to @lmayorga1980) . It works for me when I use the default network settings (just SSH port forwarding, for example) but fails when I try to use it with a private network as part of a multi-machine environment.

[lmayorga1980]

Same thing here @tricktrap when using the private_network setting.

[tricktrap]

One other thing (possibly slightly related) is that when I log into the created box, I've noticed that ifcfg-eth1 has three complete configs:

vagrant@localhost ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.33.10
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.33.10
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.33.10
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END

I suspect that the block mentioned below is doing unexpected things (like append network config to the cfg file for every retry): https://github.com/mitchellh/vagrant/blob/73fd9aa84e8ff439d2949e55a249dedb14aaf64e/plugins/guests/redhat/cap/configure_networks.rb#L52-L65

[lmayorga1980]

@tricktrap This looks interesting since its happening to me as well. I have seen other issues related to the same problem but it seems that they fix those removing this file rm -rf /etc/udev/rules.d/70-persistent-net.rules but i use packer to build the machine with different hypervisors.

[tricktrap]

@lmayorga1980 I also use packer for this. I don't even have an /etc/udev/rules.d/70-persistent-net.rules file to begin with when my shell provisioner runs, as far as I can tell. I'm pretty confident that the issue will be on my side, but it's not clear what other Vagrant boxes are doing that I'm missing.

[tricktrap]

Just to be clear, this seems to be related, or maybe identical, to #2614, except with CentOS 7 vs RHEL/CentOS 6.x. I'm going to do some more digging here, since it looks like this was fixed by an upgrade of Vagrant then.

[lmayorga1980]

@tricktrap I just took a quick look to the bento boxes https://github.com/opscode/bento/blob/master/packer/centos-7.0-x86_64.json but i could not find anything specifically created for CentOS 7.

[jedateach]

Any update on this, I'm having the same problem.
@lmayorga1980 @tricktrap - are you using VirtualBox?

[tricktrap]

@jedateach I am using the virtual box provider, yes.

[andytson]

This is caused by the bug referenced at #4171, with a fix at #4195

[mitchellh]

This is fixed by #4195