On Thursday, December 13, 2012 3:36:52 AM UTC-6, Benoit BARTHELEMY wrote:
Hi Guys !
I'm currently evaluating Puppet's cloud provisioner on vmWARE. I think I just ran into a silly localisation problem :
[root@puppet ~]# puppet node_vmware list
notice: Connecting ...
notice: Connected to myVcenter as Puppet (API version 4.1)
notice: Finding all Virtual Machines ... (Started at 10:30:37 AM)
notice: Control will be returned to you in 10 minutes at 10:40 AM if locating is unfinished.
Locating: 100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:00
notice: Complete
/Centres de données/myCluster/vm/Modeles/Linux/mymodel
powerstate: poweredOff
[...]
template: true
puppet node_vmware create --name=deploy_puppet --template="/Centres de données/myCluster/vm/Modeles/Linux/mymodel"
err: The --template option must be a path, for example /Datacenters/Solutions/vm/templates/puppet_template.
err: Try 'puppet help node_vmware create' for usage
I think the french translation of vCenter is messing up with fog, anyone experiencing the same issue ?
I am not experiencing the issue, but it is plausible that the 'é' in the path is confusing Puppet. Actually, it's more likely to be confusing the underlying Ruby, as Ruby had pretty lackluster support for varying character sets until version 1.9. Even if you're running on 1.9, I'm not sure how well Puppet uses the better character set support it provides.
Also plausible, albeit less likely, is that the spaces in the path need to be shell-escaped ("/Centres\\ de\\ données/myCluster/...").
You could try creating a symlink that bypasses the troublesome path component, and expressing the template in terms of the link. Any way around, I hope you will file a ticket.
John