2.0b1 shows incomplete multi-machine names when there are dots in the names

[samjsharpe]

I have a multi-machine setup where the machines are named foo.bar where bar denotes some kind of arbitrary grouping of machines - it seems that it's the having dots in the name which is key to this bug. When I look at the list in Vagrant Manager (2.0b1 pre-release), I see multiple machines named bar instead of the individual entries for foo1.bar, foo2.bar etc.

Here's a screenshot that shows what I mean:

The equivalent output of vagrant status is:

[gds/vagrant-govuk:master●]$ vagrant status
Current machine states:

api-lb-1.api                     not created (vmware_fusion)
api-lb-2.api                     not created (vmware_fusion)
api-mongo-1.api                  not created (vmware_fusion)
api-mongo-2.api                  not created (vmware_fusion)
api-mongo-3.api                  not created (vmware_fusion)
content-store-1.api              not created (vmware_fusion)
content-store-2.api              not created (vmware_fusion)
content-store-3.api              not created (vmware_fusion)
mysql-slave-2.backend            not created (vmware_fusion)
whitehall-mysql-master-1.backend not created (vmware_fusion)
mongo-2.backend                  not created (vmware_fusion)
<snip>

Let me know if there's any further information I can provide - the repo with multiple machines is public at https://github.com/alphagov/vagrant-govuk however unfortunately there is a separate private repo (because it contains our network and firewall details as well) from which the list of machines is loaded.

I can probably provide a sanitised copy of the machine config if you want to see my exact config.

[amitailanciano]

should be fixed by (03e1e8b58fccfebabda1dbb05d0b98f365ad7602)