bug - vagrant 1.9.4 and 1.9.5 cannot handle spaces in a vm.name

[Vince Skahan]

Vagrant 1.9.4 and 1.9.5 cannot handle spaces in the name of a virtual machine.

This is on windows 7 pro, with the latest Virtual Box (Version 5.1.22 r115126)
All versions we've tried up to and including 1.9.3 can handle this ok.

Symptoms are that Vagrant can create the vm, but you cannot 'vagrant ssh' in successfully.

Here's a trivial Vagrantfile that can be used to recreate the problem:

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "puppetlabs/centos-6.6-64-nocm"

  vm_name = "spaces test"
  config.vm.define vm_name

  config.vm.provider "virtualbox" do |vb|
     vb.gui = true
     vb.memory = "1024"
     vb.name = vm_name
  end

end

Example errors that you'll see on a subsequent 'vagrant ssh':

$ vagrant ssh
Warning: Identity file C:/Users/vds/Desktop/vag/vmbuilder/vms/.vagrant/machines/spaces not accessible: No such file or directory.
vag...@127.0.0.1's password:

Guessing this is another "somebody forgot to quote a variable" kind of thing while assembling a pathname to the ssh identity file.

[Alvaro Miranda Aguilera]

ruby on windows have the limitation.

so vagrant have the limitation,

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/120a9898-910c-4434-b92c-72ecb3c5ea01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Vince Skahan]

On Monday, June 5, 2017 at 2:55:29 PM UTC-7, Alvaro Miranda Aguilera wrote:

ruby on windows have the limitation.

so vagrant have the limitation,

Then why did it work fine in 1.9.3, 1.9.0, 1.7.4, and previous versions of vagrant we used ?

Upgrading vagrant broke this functionality.  Clearly a vagrant bug.