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

Restores vm name uniqueness. #399

Merged
merged 1 commit into from
May 2, 2019

Conversation

fretb
Copy link

@fretb fretb commented Apr 30, 2019

Fixes bug introduced by #366. By specifying a name in the Vagrantfile,
we lose uniqueness added by the Vagrant SetName
class
.
This PR restores uniqueness.

Closes #376.

Fixes bug introduced by test-kitchen#366. By specifying a name in the Vagrantfile,
we lose uniqueness added by the [Vagrant SetName
class](https://github.com/hashicorp/vagrant/blob/85acf0cac724ef4bfda593a66e0c17f7e4110da0/plugins/providers/virtualbox/action/set_name.rb#L29).
This PR restores uniqueness.

Closes test-kitchen#376.
@tas50 tas50 requested a review from cheeseplus May 1, 2019 21:31
@cheeseplus cheeseplus merged commit 94ba499 into test-kitchen:master May 2, 2019
@tas50
Copy link
Member

tas50 commented May 2, 2019

This was released in 1.5.2. Thanks @fretb

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

Successfully merging this pull request may close these issues.

kitchen-vagrant leaves a trail of semi-imported boxes if the instance name already exists
3 participants