Vagrant Destroy kills the droplet, but leaves the provider active in vagrant

[bdgeorge]

When I vagrant destroy the droplet does get destroyed, however vagrant continues to think that the provider is active. This means I can't bring the box back up with another provider.

The work around is to look in .vagrant/machines/default and delete the digital ocean provider entries.

[conorsch]

This has been biting me. As a workaround, you can simply run vagrant destroy -f a second time to clean up the machine directories. After doing so, running vagrant up can use a different provider with no conflict.

Still, it'd be wonderful if the plugin handled the cleanup as expected.

[frjaraur]

This issue still active...
Thanks