VMware Cloud Community
L2_L3
Contributor
Contributor
Jump to solution

Spec.identity.userData.computerName - Clone Workflow

Hi All-

I have been banging my ahead against the wall today trying to get the clone, Windows with single nic and credential to work.  I have it customized and it looks like it should work as intended.  I kick the workflow off and it clones the source VM (template actually) and gets to about 95% and just fails with -

A specified parameter was not correct: spec.identity.userData.computerName

I read a couple threads in which the parent item (template) contains invalid characters.  I checked and indeed my template had an _ in it.  Deleted it and created a new template, all letters and numbers and well under the 15 character limit.  Updated the attribute to point to this and the same error.  My new VM is getting its potential name from an input parameter.  I am seeing also this in the orchestrator logs.

[2016-06-24 15:52:27.124] [E] Error in (Dynamic Script Module name : vim3WaitTaskEnd#20) Task 'CloneVM_Task' error: A specified parameter was not correct: spec.identity.userData.computerName

[2016-06-24 15:52:27.184] [E] Workfow execution stack:

***

item: 'Clone, Windows 2012R2 Standard/item2', state: 'failed', business state: 'Cloning', exception: 'Task 'CloneVM_Task' error: A specified parameter was not correct: spec.identity.userData.computerName (Dynamic Script Module name : vim3WaitTaskEnd#20)

Then this within the vpxa logs


-->    name = "testest",

-->    sanitizedName = "testest",

-->    folder = 'vim.Folder:a1c562b8-bf8c-4e6c-8043-49bb3c78c121:group-v202',

-->    tempSnapshotName = <unset>,

-->    checkpointFileName = <unset>,

-->    vAppClone = false,

-->    macAssignmentData = (string) [

-->       "00:50:56:b0:13:95"

-->    ],

-->    forkCtx = (vpx.vmprov.ForkContext) null,

--> }

2016-06-24T15:42:42.588-05:00 info vpxd[97304] [Originator@6876 sub=vpxLro opID=cell-e61974cc-180b-4827-b36a-58ae466f90f5-8b] [VpxLRO] -- BEGIN task-internal-24957147 -- domain-c277 -- vim.ComputeResource.GetEnvironmentBrowser -- 52af655b-28cb-6800-c2ff-5e20b13b1f40(52be3fe9-2ec3-2a57-14fa-25a64f69c39e)

2016-06-24T15:42:42.592-05:00 error vpxd[112256] [Originator@6876 sub=vpxLro opID=2572d454-79] [VpxLRO] Unexpected Exception: vmodl.fault.InvalidArgument

2016-06-24T15:42:42.592-05:00 info vpxd[112256] [Originator@6876 sub=vpxLro opID=2572d454-79] [VpxLRO] -- FINISH task-internal-24955876

2016-06-24T15:42:42.592-05:00 info vpxd[112256] [Originator@6876 sub=Default opID=2572d454-79] [VpxLRO] -- ERROR task-internal-24955876 --  -- VmprovWorkflow: vmodl.fault.InvalidArgument:

--> Result:

--> (vmodl.fault.InvalidArgument) {

-->    faultCause = (vmodl.MethodFault) null,

-->    invalidProperty = "spec.identity.userData.computerName",

-->    msg = ""


One vcenter, only using IPs, no hostnames, one of the datastores does have _ scores, tried others.  Have disabled drs, storage drs, just in case.
I have triple checked everything - org name, full name, etc.  I am out of ideas of what to look for, can anyone please shed some ideas on what I could try?

0 Kudos
1 Solution

Accepted Solutions
adamwiso
Enthusiast
Enthusiast
Jump to solution

So looking at your workflow, you had "clientName" set as a string and left blank (easy one to miss).  In my environment I set this to the template name and during deployment and after sysprep it kept this static name and did not change to the VM "name".  To work around this I just deleted the attribute "clientName" and then just mapped "name -> clientName" in the Get Windows Customization element in visual binding tab, this should do it for you.

View solution in original post

0 Kudos
5 Replies
L2_L3
Contributor
Contributor
Jump to solution

Still battling why this is happening, going to try this in another environment tonight.  In the vpxd logs seeing what looks like it sets the name, then it shows invalid property.  Hits a task loop, fails again, then shows argument (arg spec: vim.vm.CloneSpec) would anyone know why that is.  The actual schema element "Clone VM" has 4 "IN" parameters, folder:folder attribute, name:name in-parameter, spec: spec attribute, and vm:vm attribute and one "OUT" actionResult: task attribute

My "task" attribute has name of task, type VC:Task and value as not set, does this need to be set to a value?  In the original workflow in which from I duplicated this is not set.

Does anyone have any ideas what I could be missing or give me any other places to look?

-->    name = "testtest",

-->    sanitizedName = "testtest",

-->    folder = 'vim.Folder:a1c562b8-bf8c-4e6c-8043-49bb3c78c121:group-v202',

-->    tempSnapshotName = <unset>,

-->    checkpointFileName = <unset>,

-->    vAppClone = false,

-->    macAssignmentData = (string) [

-->       "00:50:56:b0:7c:96"

-->    ],

-->    forkCtx = (vpx.vmprov.ForkContext) null,

--> }

2016-06-29T15:57:54.468-05:00 error vpxd[10328] [Originator@6876 sub=vpxLro opID=63488043-7b] [VpxLRO] Unexpected Exception: vmodl.fault.InvalidArgument

2016-06-29T15:57:54.468-05:00 info vpxd[10328] [Originator@6876 sub=vpxLro opID=63488043-7b] [VpxLRO] -- FINISH task-internal-12924485

2016-06-29T15:57:54.468-05:00 info vpxd[10328] [Originator@6876 sub=Default opID=63488043-7b] [VpxLRO] -- ERROR task-internal-12924485 --  -- VmprovWorkflow: vmodl.fault.InvalidArgument:

--> Result:

--> (vmodl.fault.InvalidArgument) {

-->    faultCause = (vmodl.MethodFault) null,

-->    invalidProperty = "spec.identity.userData.computerName",

-->    msg = ""

--> }

--> Args:

-->

2016-06-29T15:57:54.471-05:00 warning vpxd[09952] [Originator@6876 sub=VpxProfiler opID=63488043-7b-TaskLoop-ddea02e] TaskLoop [TotalTime] took 40237 ms

2016-06-29T15:57:54.477-05:00 info vpxd[10328] [Originator@6876 sub=vpxLro opID=63488043] [VpxLRO] -- FINISH task-1400

2016-06-29T15:57:54.477-05:00 info vpxd[10328] [Originator@6876 sub=Default opID=63488043] [VpxLRO] -- ERROR task-1400 -- vm-310 -- vim.VirtualMachine.clone: vmodl.fault.InvalidArgument:

--> Result:

--> (vmodl.fault.InvalidArgument) {

-->    faultCause = (vmodl.MethodFault) null,

-->    invalidProperty = "spec.identity.userData.computerName",

-->    msg = ""

--> }

--> Args:

-->

--> Arg folder:

--> 'vim.Folder:group-v202'

--> Arg name:

--> "testtest"

--> Arg spec:

--> (vim.vm.CloneSpec) {

-->    location = (vim.vm.RelocateSpec) {

-->       service = (vim.ServiceLocator) null,

-->       folder = 'vim.Folder:a1c562b8-bf8c-4e6c-8043-49bb3c78c121:group-v202',

-->       datastore = 'vim.Datastore:a1c562b8-bf8c-4e6c-8043-49bb3c78c121:datastore-13',

-->       diskMoveType = <unset>,

-->       pool = 'vim.ResourcePool:a1c562b8-bf8c-4e6c-8043-49bb3c78c121:resgroup-8',

-->       host = 'vim.HostSystem:a1c562b8-bf8c-4e6c-8043-49bb3c78c121:host-27',

-->       transform = <unset>,

-->       profile = (vim.vm.ProfileSpec) [

-->          (vim.vm.EmptyProfileSpec) {

-->          }

0 Kudos
adamwiso
Enthusiast
Enthusiast
Jump to solution

Sent you a message, export the workflow and send it over to the email in the DM.  Will take a look see if I can see anything not quite lining up.

0 Kudos
adamwiso
Enthusiast
Enthusiast
Jump to solution

So looking at your workflow, you had "clientName" set as a string and left blank (easy one to miss).  In my environment I set this to the template name and during deployment and after sysprep it kept this static name and did not change to the VM "name".  To work around this I just deleted the attribute "clientName" and then just mapped "name -> clientName" in the Get Windows Customization element in visual binding tab, this should do it for you.

0 Kudos
L2_L3
Contributor
Contributor
Jump to solution

Big Thank you!  Worked perfect.

0 Kudos
chr1s86
Enthusiast
Enthusiast
Jump to solution

I have the exact same issue. Don't find where to fix it. Could you help me?

Blog: http://vblog.hochsticher.de/
0 Kudos