On Sunday, December 11, 2016 at 9:32:47 AM UTC-7, Alvaro Miranda Aguilera
wrote:
>
> no need for that.
>
> just add in the meantime
>
> config.vm.provision "shell", inline: "ifup eth1", run: "always"
>
>
> On Sat, Dec 10, 2016 at 10:27 PM, Matthew Pounsett <[email protected]
> <javascript:>> wrote:
>
>>
>>
>> On Saturday, 10 December 2016 15:11:46 UTC-5, Alvaro Miranda Aguilera
>> wrote:
>>>
>>>
>>> Vagrant version?
>>> host os?
>>>
>>
>> Hmm... Yeah, sorry. Not sure why I didn't paste those in to the original
>> email.
>> I'm using Vagrant 1.9.1 on MacOS 10.10.5
>>
>>
>>>
>>> Can you share a gist to the output of
>>>
>>> VAGRANT_LOG=debug
>>> vagrant up
>>>
>>
>> absolutely.
>> <https://gist.github.com/mpounsett/e432cf60d7e7111231f9c2d1de4d00ce>
>>
>> It looks to me like the bug you noted in your other post... should be
>> fixed in 1.9.2.
>> I have been using a reboot at the end of my provisioning script as a
>> workaround. That should be fine until the patch makes it out into the
>> MacOS distribution.
>>
>> Thanks!
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/29b48573-c01a-452e-98e9-b3848cbcb13b%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/vagrant-up/29b48573-c01a-452e-98e9-b3848cbcb13b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
>
I'm having the same issue. Glad it's not just me. I just started reading
Jeff Geerlings Ansible book and am new to Vagrant and Ansible, so I figured
it was my inexperience that was the problem. In my case enp0s8 is created
but is not up. If I do it with a ubuntu/trusty64 box it works fine.
Thanks,
Mark
[root@localhost ansible3]# cat Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "geerlingguy/centos7"
config.vm.network "private_network", ip: "192.168.60.4"
end
[root@localhost ansible3]# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'geerlingguy/centos7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'geerlingguy/centos7' is up to date...
==> default: Setting the name of the VM:
ansible3_default_1481503419064_90554
==> default: Fixed port collision for 22 => 2222. Now on port 2202.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2202 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2202
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically
replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH
key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /vagrant => /home/ansible3
[root@localhost ansible3]# vagrant ssh
[vagrant@localhost ~]$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 08:00:27:d0:79:66 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic enp0s3
valid_lft 86375sec preferred_lft 86375sec
inet6 fe80::a00:27ff:fed0:7966/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen
1000
link/ether 08:00:27:ec:c9:f1 brd ff:ff:ff:ff:ff:ff
[vagrant@localhost ~]$
[vagrant@localhost network-scripts]$ more ifcfg-enp0s8
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.60.4
NETMASK=255.255.255.0
DEVICE=enp0s8
PEERDNS=no
#VAGRANT-END
[vagrant@localhost network-scripts]$
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/5a0f85c9-aa62-4bff-a3e6-921282885657%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
