Fix for broken vagrant installs when using Vagrant 1.8.5. 69/2169/3
authorThomas F Herbert <thomasfherbert@gmail.com>
Mon, 1 Aug 2016 22:33:48 +0000 (18:33 -0400)
committerKeith Burns <alagalah@gmail.com>
Tue, 2 Aug 2016 14:20:21 +0000 (14:20 +0000)
commit7b75d211ae7b28ace7c6eee8e00005a0c45df45d
tree14401808bee174db1790c010cb4284b4916ff294
parent734d291c2e587b4760984cf75a50912c69106bdf
Fix for broken vagrant installs when using Vagrant 1.8.5.

I upgraded Fedora23 which installed kernel 4.6.4 which in turn required
VirtualBox 5.1.2 which in turn required Vagrant 1.8.5.

Workaround for a change in Vagrant 1.8.5 that breaks Centos. The
newer version of Vagrant doesn't chmod the ssh directory before trying to copy
new public key during installs. This will be fixed upstream in Vagrant 1.8.6.
Bug doesn't affect Ubuntu because it uses a different umask whereas Centos uses
0002.

Change-Id: I8108d4cc208fc47fa69f8a5cf27b2bba7e34293e
Signed-off-by: Thomas F Herbert <therbert@redhat.com>
build-root/vagrant/Vagrantfile