/etc/hosts is not updated on vdestroy about oh-my-vagrant HOT 3 CLOSED

@scollier the hostmanager plugin will ensure the /etc/hosts files matches the vagrant reality of defined machines, IOW what you see when you run vagrant status. This means even if a machine is "destroyed", it's still defined. You define machines in omv by setting the vms variable and/or count variable in omv.yaml. If you don't want a machine to appear in /etc/hosts remove it from the omv.yaml definition.

Please note, when you change this, the vms will be renumbered if you haven't statically set IP addresses.
So if you remove master 2, master3 will get the ip 192.168.123.102.

Lastly, please explain the problem you are having that entries in /etc/hosts are causing you :)

from oh-my-vagrant.

The problem is that the message states that ==> node1: Updating /etc/hosts file on active guest machines... it is cleaning up the environment. It's not causing any immediate issues, but it's certainly not adding anything useful. I'd rather not have entries in my hosts file that don't exist.

Now, if the host file is configured per defined machines, then that's one thing. However, the message says active guest machines. It doesn't say defined machines.

from oh-my-vagrant.

@scollier I understand your point, however those are things/design choices (even if they are bugs) that vagrant defined, not oh-my-vagrant. OMV just wraps whatever vagrant does to make that part easier. I'd love to offer you a better solution, but for the moment, I have no ideas.

Either send a patch here or upstream if you think of something, and open a new ticket if there's a fix I didn't think of.

Cheers!

from oh-my-vagrant.