vSphere 5.1 is not supported, and I’ve observed some differences in the way it handles extra config variables like the opennebula.context one. Do you have access to vSphere 5.5 or 6.0 to confirm this behaviour?
Hi Tino, do you think this issue is also valid for a vcenter 5.5 environment with esxi5.1 hosts? I’v this kind of infrastructure and contextualization doesn’t work.
Can you send through the content of the deployment file?
/var/lib/one/vms//deployment.0
If this is correct, the next step would be to run a deployment manually with some debug information to see if the value is passed correctly to vCenter.