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.

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

Improving resilience of some VirtualBox commands fixup #8951

Merged
merged 4 commits into from Sep 6, 2017

Conversation

briancain
Copy link
Member

@briancain briancain commented Sep 6, 2017

This pull request fixes up and rebases PR #8525

It also brings in the changes from this PR: #8464

Fixes #8468

nicolasvan and others added 4 commits September 6, 2017 11:13
ignoring VMs that may have been deleted between the calls to
'vboxmanage list vms' and 'vboxmanage showvminfo'
…networks function by

ignoring VMs that may have been deleted between the calls to
'vboxmanage list vms' and 'vboxmanage showvminfo'
Issue: hashicorp#8468

A lot of vboxmanage commands are flakey and frequently cause
bringing multiple machines up at once to fail, especially when
the host system is under heavy load. Most commands are also safe
to retry and just result in a no-op, so we can simply add
'retryable' to a lot of existing calls. For the others we need to
do a little bit of cleanup or reevaluate the parameters before
trying again.
Reverting the changes done in 7d2f7da
because they don't work and or update vagrant to invoke running the
vbox cli tool for every single forwarded port instead of forwarding them
all in one command.
@briancain briancain changed the title Fixup of "8468 - make more virtualbox commands retryable" Improving resilience of some VirtualBox commands fixup Sep 6, 2017
@briancain briancain merged commit b2f34a6 into hashicorp:master Sep 6, 2017
@briancain briancain deleted the RETRYABLE-COMMANDS branch October 2, 2018 17:40
@ghost
Copy link

ghost commented Mar 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fresh vagrant up fails due to machine being locked
3 participants