vagrant-hostmanager icon indicating copy to clipboard operation
vagrant-hostmanager copied to clipboard

setting Stale/Ghost hosts attempts

Open jayunit100 opened this issue 9 years ago • 1 comments

When using vagrant openstack, I find that vagrant hostmanager reports that "machine with the name 12345-1 was not configured for this environment".

This is a fatal error .

However, those machines were deleted (using vagrant global-status --prune confirms this).

I've even grepped around for those particular machine names, and they are nowhere to be found.

Is there some hidden state somewhere that is caching machine names that i can reset?

possibly this is just an issue that vagrant openstack is providing machine names to the hostmanager and REST api calls are returning machines which no longer exist. But even so, i think hostmanager should be smart enough not to try to update a hosts file to include a machine that no longer is reachable.

jayunit100 avatar Jul 01 '15 16:07 jayunit100

FYI rm -rf .vagrant/ seems to fix this. to reproduce the trick is to create a bunch of VMs that cannot be recreated (i.e. change the vagrantfile after you create them), and then run vagrant up. The result is that the last batch of created VMs won't be found, so hostmanager dies.

jayunit100 avatar Jul 01 '15 20:07 jayunit100