Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Query VMs state on startup #7

Open
candidtim opened this issue Apr 14, 2015 · 1 comment
Open

Query VMs state on startup #7

candidtim opened this issue Apr 14, 2015 · 1 comment
Labels
enhancement help wanted

Comments

@candidtim
Copy link
Owner

It is often the case that some VMs may be left in an "inconsistent" state after system restart: some running VMs may have been killed while this will be not tracked in vagrant's machine-index, which is used as the data source for the indicator. As a result, after restart, Vagrant AppIndicator shows VMs as running, while they are actually shut down.

As Vagrant's machine-index doesn't provide means to track these changes made outside of Vagrant, AppIndicator might query Vagrant to find out the states of all known machines. Querying just once att AppIndicator start will cover most of the desynchronization cases.
@candidtim
Copy link
Owner Author

Note, vagrant global-status --prune seems to do the thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@candidtim