From a8e1cd63db381a07bff029f99c30ba52cac963d3 Mon Sep 17 00:00:00 2001 From: Tim Kuhlman Date: Thu, 15 Jan 2015 13:27:48 -0700 Subject: [PATCH] Fix ansible for newer vagrant versions. Change-Id: If17b4be090c2c46c62c8273a2f82366d09945edb --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0dc1582..93cf4a8 100644 --- a/README.md +++ b/README.md @@ -141,9 +141,13 @@ your local ansible configuration (~/.ansible.cfg or a personal ansible.cfg in th [defaults] hostfile = .ansible_hosts - private_key_file = ~/.vagrant.d/insecure_private_key remote_user = vagrant host_key_checking = False + # Note: For newer versions of Ansible a single insecure_private_key isn't used, rather it is machine specific + # by modifying .ansible_hosts adding ansible_ssh_key_file to the end of the line you can configure the proper behavior. + # In that case leave out the private_key_file line below. + # For example `devstack ansible_ssh_host=192.168.10.5 ansible_ssh_private_key_file=.vagrant/machines/devstack/virtualbox/private_key` + private_key_file = ~/.vagrant.d/insecure_private_key # In some configurations this won't work, use only if your config permits. #[ssh_connection]