I actually added this as a Stackoverflow question too.. FYI
https://stackoverflow.com/questions/58752300/why-does-vagrant-global-status-not-work-but-local-status-does
Context
Vagrant 2.2.5
Windows 10, everything was working fine. A different issue caused my disk
space to be used up, I tried to vagrant destroy {id} and the destroy failed
due to not enough disk space.
After that, running vagrant global-status says I have no active
environments.
Symptoms
vagrant global-status says I have no environments.
If I open VirtualBox directly it can see all my Vagrant VMs listed.
If I compare the IDs for the VMs from VBox to the IDs in the .vagrant
folders they match.
And finally, if I run vagrant status from the local project path,
everything works fine. I can up, halt, destroy, I can ssh into them fine.
The only thing that doesn't work is global-status.
Why?
Thanks all!
Andy
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/ebd649d2-5252-4ea3-af2c-62b65b272e45%40googlegroups.com.
