Describe the bug
A clear and concise description of what the bug is.
sometimes, .vagrant/machines/ contains machine confs from another splunk_config.yml or something, and the host-manager plugin generates the following error:
The machine with the name xxx was not found configured for this Vagrant environment
To Reproduce
Steps to reproduce the behavior:
provide splunk_config.yml
provide exact commands you executed
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. Linux, OSX]
Ansible Version [ansible --version]
Additional context
Add any other context about the problem here.
You have to destroy the the machines first, before you built new ones. There is also not problem to remove the .vagrant directory manually and delete the machines in the virtualbox gui by hand.
Describe the bug A clear and concise description of what the bug is. sometimes, .vagrant/machines/ contains machine confs from another splunk_config.yml or something, and the host-manager plugin generates the following error:
The machine with the name xxx was not found configured for this Vagrant environment
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.