So this is really odd. We have a customer who's been happily creating blueprints and virtual machines for a while. Nothing overly complex
They have a standard code block that reads
Cloud_vSphere_Machine_1:
type: Cloud.vSphere.Machine
properties:
newName :'THEIRPREFIX$(input.Hostname)'
etc.....
They enter in a suffix - usually just a number that gets appended to their hostname. That is working fine, they have many VMs created this way.
Recently they copied this blueprint and changed the prefix. No other changes. Despite showing the correct newname in the deployment under the Cloud_vSphere_Machine_1 custom properties as with the working ones the VM gets created with the generic Cloud_vSphere_Machine_1-mcmxxx-xxxxxxxxxxxx name in vCenter. This has a knock on effect because in addition to the name issue some template scripts that join the domain etc then fail.
I then tried cloning the ORIGINAL blueprint myself making NO changes and deploying from that. I get the same problem with the machine not renaming. However running a deployment from the original blueprint itself works fine and the machine is renamed correctly.
Does anyone have any ideas before I go to support?
