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

Machine with name 'someolduselessdeletedvm' not configured #258

Open
rvolgers opened this issue Apr 5, 2018 · 0 comments
Open

Machine with name 'someolduselessdeletedvm' not configured #258

rvolgers opened this issue Apr 5, 2018 · 0 comments

Comments

@rvolgers
Copy link

rvolgers commented Apr 5, 2018

This appears to be the same issue as #102, but nothing there worked for me. Still looking for a solution. (Edit: Problem has since been solved, I was clearing files in the wrong .vagrant directory. The question below is therefore still relevant but a lot less pressing for me now :) )

But more importantly, can anybody explain WHY this is a fatal error instead of a warning? I would very much like to get on with my work and solve this seemingly minor problem later. Is this problem really important enough to refuse to let the user do anything until it is fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant