hostmanager runs when destroying host

[utdrmac]

Why does the hostmanager attempt to update the hosts file when destroying the instance?

[drmac@othala vagrant-percona]$ vagrant destroy -f
==> consul3: Terminating the instance...
==> consul3: Updating /etc/hosts file on active guest machines...
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.

[utdrmac]

More of this on local virtualbox. Doesn't seem to cause as much of an issue compared to AWS.

[drmac@othala vagrant-percona]$ vagrant destroy -f
==> client1: Forcing shutdown of VM...
==> client1: Destroying VM and associated drives...
==> client1: Updating /etc/hosts file on active guest machines...
==> consul3: Forcing shutdown of VM...
==> consul3: Destroying VM and associated drives...
==> consul3: Updating /etc/hosts file on active guest machines...
==> consul2: Forcing shutdown of VM...
==> consul2: Destroying VM and associated drives...
==> consul2: Updating /etc/hosts file on active guest machines...
==> consul1: Forcing shutdown of VM...
==> consul1: Destroying VM and associated drives...
==> consul1: Updating /etc/hosts file on active guest machines...

[caveman-dick]

This is causing me an issue too. I'm using windows images that have the vagrant user account with password expiry enabled. Once the password expires winrm fails and crashes out the destroy command when trying to update the hosts file on the remaining boxes.

IMO If there is no filter on the destroy command it should skip over any hostmanager tasks.