Suspended VM displayed as "running" in global-status until vagrant status is run

[tuminoid]

Suspended VM state is displayed as "running" in global-status, unless you manually execute status for that VM. Which kinda defeats the purpose of global-status.

Using Vagrant 1.6.5 on Ubuntu 14.04.

$ vagrant suspend
==> default: Saving VM state and suspending execution...

$ vagrant global-status
id       name        provider   state   directory                                    
-------------------------------------------------------------------------------------
dbfffec  default     virtualbox running /home/tumi/git/fake-package-creator 

$ vagrant status
Current machine states:

default                   saved (virtualbox)

To resume this VM, simply run `vagrant up`.

$ vagrant global-status
id       name        provider   state   directory                                    
-------------------------------------------------------------------------------------
dbfffec  default     virtualbox saved   /home/tumi/git/fake-package-creator 

[mitchellh]

This is working as intended. The docs state that global-status is a cache. If you run --prune, it will update all of them. Global status is meant to give you an at-a-glance view of a cache.

However, we do our best to make sure it is always updated. Going to try to investigate to see if there is something we can do here.

[tuminoid]

Cache could be updated when you run basic state actions like up, destroy and halt. global-status shouldn't be the one doing the cache update, but as you said, just print the cache.

[mitchellh]

Yeah, it should be... that's why I'm taking a look. :)

[mitchellh]

Fixed!

[aspiers]

This change has either directly or indirectly caused #4717.

[mwrock]

I think this is fixed by PR #4792