Fix error message for host-only network collision #340
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In Vagrant v2.0.4 the exception "Vagrant::Errors::NetworkCollision" class has been modified. We port it locally here in order to keep backward compatibility with older Vagrant versions
legal90
force-pushed
the
fix-network-collision-msg
branch
from
3c6a522 to
17d5b1c
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #339
In Vagrant v2.0.4 the exception
Vagrant::Errors::NetworkCollisionclass has been modified, 2 arguments were added: hashicorp/vagrant#9685We port it locally here in order to keep backward compatibility with older Vagrant versions.