On Monday, December 12, 2016 at 9:12:13 AM UTC-7, Will Seaford wrote:
>
> I have just had this problem myself and found the latest version was
> messing it up for me. By changing from 1.9.1 to 1.8.6. This solved my
> problem.
>
>>
>>
Already running vagrant 1.9.1 on a CentOS 7 host:
[root@localhost ansible3]# vagrant --version
Vagrant 1.9.1
[root@localhost ansible3]# cat /etc/red*
CentOS Linux release 7.2.1511 (Core)
The good news is that Alvaro's workaround worked! Thank you!!!
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 08:00:27:18:44:89 brd ff:ff:ff:ff:ff:ff
inet 192.168.60.4/24 brd 192.168.60.255 scope global enp0s8
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe18:4489/64 scope link
valid_lft forever preferred_lft forever
--
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/119f5af0-a81d-4657-9cad-616f65c2a269%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
