then BEFORE worked nice for me!
Vagrant 1.2.7
CentOS 6.4
I modified the box (http://developer.nrel.gov/downloads/vagrant-boxes/CentOS-6.4-i386-v20130427.box) like installing httpd, mysql, etc, then simply packaged it. After that, I attempted to vagrant this package up. But following error came up.
[node1] Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! /sbin/ifup eth1 2> /dev/null
So I did
However this also gave me the same error and both 70-persistent-net.rule and ifcfg-eth1 files are regenerated.
After reloading the VM, ifcfg-eth1 is looked like this.
#VAGRANT-BEGIN # The contents below are automatically generated by Vagrant. Do not modify. BOOTPROTO=none 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. BOOTPROTO=none 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. BOOTPROTO=none IPADDR=192.168.33.10 NETMASK=255.255.255.0 DEVICE=eth1 PEERDNS=no #VAGRANT-END
Not related to how many times I did this VM, the description in ifcfg-eth1 was repeated 3 times.
Though this doesn't seem to be the cause of this issue, this was perhaps written by following script in vagrant-1.2.7/plugins/guests/redhat/cap/configure_networks.rb, t
48 retryable(:on => Vagrant::Errors::VagrantError, :tries => 3, :sleep => 2) do
49 machine.communicate.sudo("/sbin/ifdown eth#{interface} 2> /dev/null", :error_check => false)
50 machine.communicate.sudo("cat /tmp/vagrant-network-entry_#{interface} >> #{network_scripts_di r}/ifcfg-eth#{interface}")
51 machine.communicate.sudo("ARPCHECK=no /sbin/ifup eth#{interface} 2> /dev/null")
52 end
Hope this issue to be fixed :)
注册有任何问题请添加 微信:MVIP619 拉你进入群
打开微信扫一扫
添加客服
进入交流群
发表评论