cygdrive/c/Work/TEST_BOX/C:/Work/TEST_BOX/.vagrant/provisioners/ansible/inventory did not meet host_list requirements, check plugin documentation if this is unexpected Using /cygdrive/c/Work/TEST_BOX/ansible.cfg as config file $ PYTHONUNBUFFERED=1 ANSIBLE_NOCOLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook -connection=ssh -timeout=30 -limit="default" -inventory-file=C:/Work/TEST_BOX/.vagrant/provisioners/ansible/inventory -v provisioning/tamerbook.yml We will take out the provisioning command shown in the above debug output of vagrantĪnd lets try running it directly that might give us an idea of what’s going on. So ansible is installed lets see what is the problem. however $ ansible -versionĬonfig file = /cygdrive/c/Work/TEST_BOX/ansible.cfgĬonfigured module search path = Īnsible python module location = /usr/lib/python2.7/site-packages/ansible Interesting so it seems ansible is not detected. Vagrant can't do this for you in a safe and
#Vagrant ansible install
If you haven't installed Ansible yet, please install Ansible That Ansible is correctly installed on your host system.
#Vagrant ansible software
The Ansible software could not be found! Please verify PYTHONUNBUFFERED=1 ANSIBLE_NOCOLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook -connection=ssh -timeout=30 -limit="default" -inventory-file=C:/Work/TEST_BOX/.vagrant/provisioners/ansible/inventory -v provisioning/tamerbook.yml Windows is not officially supported for the Ansible Control Machine. => default: Running provisioner: ansible. => default: Configuring and enabling network interfaces. If you seeĭefault: shared folder errors, please make sure the guest additions within theĭefault: virtual machine match the version of VirtualBox you have installed on => default: Checking for guest additions in VM.ĭefault: The guest additions on this VM do not match the installed version ofĭefault: VirtualBox! In most cases this is fine, but in rare cases it canĭefault: prevent things such as shared folders from working properly.
This may take a few minutes.ĭefault: Inserting generated public key within guest.ĭefault: Removing insecure key from the guest if it's present.ĭefault: Key inserted! Disconnecting and reconnecting using new SSH key. => default: Preparing network interfaces based on configuration.ĭefault: 22 (guest) => 2222 (host) (adapter 1)
=> default: Clearing any previously set network interfaces. => default: Matching MAC address for NAT networking. => default: Importing base box 'tamer_debian10'. name: install packages essential for ansible+vagrant stuffīringing machine 'default' up with 'virtualbox' provider. Sample playbook provisioning/tamerbook.yml -Īnd a essentials role file “provisining/roles/essentials/tasks/main.yml”. Sample Vagrantfile in use # -*- mode: ruby -*-ĮNV = 'virtualbox'Ĭonfig.vm.network "private_network", type: "dhcp"Ĭonfig.vm.provision "ansible" do | ansible|Īaybook = "provisioning/tamerbook.yml" Ansible is installed on system using the cygwin admin console and pip2 install ansible
#Vagrant ansible full
We have a full installation of cygwin and will be using cygwin bash for this experiment.Ĥ. For the setup what i have is a Local User with limited privileges lets call him “Anant Shrivastava”, and a local admin lets call him anant.ģ. I want to make sure i don’t lose this experiment hence documenting it out in a quick blog postġ.
#Vagrant ansible series
Its a fun experiment coz ansible never claimed to support windows as control device and the solution is a series of workaround and gotcha’s that i have listed so far. Recently i was asked to help someone run vagrant ansible combination on windows.
0 kommentar(er)
