VMware Aria Automation Orchestrator

 View Only
  • 1.  A specified parameter was not correct: spec.identity.hostName

    Posted Feb 03, 2023 09:20 PM

    Hi Guys  i currently made a debian vm in vcenter and converted it into   a template. My plan is to deploy vm machines using this template from vrealize orchastrator. I have posted my workflow and the error that i am getting. It has a problem with the host name but the host name is "temp" which i dont see a problem with. I  am new to vrealize and would appreciate any help.



  • 2.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 04, 2023 12:21 AM

    Can you show the code in Clone Linux subflow?



  • 3.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 04, 2023 08:20 AM
      |   view attached

    Hey thanks for the quick answer. Hier is the pic.



  • 4.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 04, 2023 09:06 AM

    var taskEnd = false;
    var error;

    while (task != null) {
    if (task.info == null) {
    throw "VIM Task info is null";
    }
    if (task.info.state == null) {
    throw "VIM Task state is null";
    }

    var state = task.info.state.value;
    if (state == "success") {
    break;
    }
    else if (state == "error") {
    if (task.info.error.localizedMessage == null) {
    throw "Task '" + task.info.name + "' has encountered an unknown error";
    }
    else {
    throw "Task '" + task.info.name + "' error: "+task.info.error.localizedMessage;
    }
    }
    else if ((progress) && (state == "running")) {
    if (task.info.progress == null) {
    System.log(task.info.name+" Queued or In Progress...");
    }
    else {
    System.log(task.info.name+" "+task.info.progress+" %");
    }
    }
    System.sleep(pollRate*1000);
    }

    if (task == null) {
    throw "VIM Task is null";
    }
    else if (progress) {
    System.log(task.info.name+" end");
    }

    System.sleep(2*1000);

    // Return the Task Result
    if (task != null && task.info != null && task.info.result != null) {
    return VcPlugin.convertToVimManagedObject(task , task.info.result);
    }
    else {
    return null;
    }



  • 5.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 04, 2023 09:08 AM

    As the problem is with custom spec, can you post the code where you set the hostname?



  • 6.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 06, 2023 09:51 AM
      |   view attached

    I found the problem it was an attribute which was wrong. But i have another problem and it is the task of adding an extra disk. 

    2023-02-06 10:14:09.998 +01:00INFO__item_stack:/item1
    2023-02-06 10:14:10.009 +01:00INFO__item_stack:/item1/item11
    2023-02-06 10:14:10.027 +01:00INFO__item_stack:/item1/item0
    2023-02-06 10:14:10.045 +01:00INFO__item_stack:/item1/item1
    2023-02-06 10:14:10.054 +01:00INFO__item_stack:/item1/item8
    2023-02-06 10:14:10.069 +01:00INFO__item_stack:/item1/item5
    2023-02-06 10:14:10.082 +01:00INFO__item_stack:/item1/item5/item0
    2023-02-06 10:14:10.091 +01:00INFO__item_stack:/item1/item5/item1
    2023-02-06 10:14:10.101 +01:00INFO__item_stack:/item1/item5/item2
    2023-02-06 10:14:10.112 +01:00INFO__item_stack:/item1/item9
    2023-02-06 10:14:10.130 +01:00INFO__item_stack:/item1/item9/item3
    2023-02-06 10:14:10.139 +01:00INFO__item_stack:/item1/item9/item6
    2023-02-06 10:14:10.147 +01:00INFO__item_stack:/item1/item9/item5
    2023-02-06 10:14:10.156 +01:00INFO__item_stack:/item1/item9/item2
    2023-02-06 10:14:10.164 +01:00INFO__item_stack:/item1/item9/item1
    2023-02-06 10:14:10.173 +01:00INFO__item_stack:/item1/item9/item0
    2023-02-06 10:14:10.187 +01:00INFO__item_stack:/item1/item10
    2023-02-06 10:14:10.197 +01:00INFO__item_stack:/item1/item7
    2023-02-06 10:14:10.212 +01:00INFO__item_stack:/item1/item6
    2023-02-06 10:14:10.231 +01:00INFO__item_stack:/item1/item23
    2023-02-06 10:14:10.240 +01:00INFOFound a Virtual Ethernet card at 12. Key: 4000
    2023-02-06 10:14:10.253 +01:00INFO__item_stack:/item1/item24
    2023-02-06 10:14:10.263 +01:00INFO__item_stack:/item1/item27
    2023-02-06 10:14:10.275 +01:00INFO__item_stack:/item1/item22
    2023-02-06 10:14:10.298 +01:00INFO__item_stack:/item1/item22/item3
    2023-02-06 10:14:10.312 +01:00INFO__item_stack:/item1/item22/item13
    2023-02-06 10:14:10.326 +01:00INFO__item_stack:/item1/item22/item4
    2023-02-06 10:14:10.342 +01:00INFO__item_stack:/item1/item22/item0
    2023-02-06 10:14:10.355 +01:00INFO__item_stack:/item1/item22/item16
    2023-02-06 10:14:10.366 +01:00INFO__item_stack:/item1/item22/item1
    2023-02-06 10:14:10.389 +01:00INFO__item_stack:/item1/item22/item2
    2023-02-06 10:14:10.400 +01:00INFO__item_stack:/item1/item22/item11
    2023-02-06 10:14:10.409 +01:00INFO__item_stack:/item1/item22/item12
    2023-02-06 10:14:10.431 +01:00INFO__item_stack:/item1/item22/item14
    2023-02-06 10:14:10.455 +01:00INFO__item_stack:/item1/item22/item9
    2023-02-06 10:14:10.470 +01:00INFO__item_stack:/item1/item25
    2023-02-06 10:14:10.489 +01:00INFO__item_stack:/item1/item26
    2023-02-06 10:14:10.505 +01:00INFO__item_stack:/item1/item4
    2023-02-06 10:14:10.522 +01:00INFO__item_stack:/item1/item3
    2023-02-06 10:14:10.571 +01:00INFO__item_stack:/item1/item2
    2023-02-06 10:14:42.635 +01:00INFO__item_stack:/item1/item13
    2023-02-06 10:14:42.651 +01:00INFO__item_stack:/item1/item12
    2023-02-06 10:14:42.663 +01:00INFO__item_stack:/item1/item15
    2023-02-06 10:14:42.702 +01:00INFO__item_stack:/item1/item17
    2023-02-06 10:16:22.748 +01:00INFOFound name 't0test05' for VM 't0test05'
    2023-02-06 10:16:22.762 +01:00INFO__item_stack:/item1/item18
    2023-02-06 10:16:22.772 +01:00INFO__item_stack:/item1/item20
    2023-02-06 10:16:22.782 +01:00INFO__item_stack:/item1/item20/item0
    2023-02-06 10:16:22.810 +01:00INFO__item_stack:/item1/item20/item1
    2023-02-06 10:16:29.037 +01:00INFO__item_stack:/item1/item20/item4
    2023-02-06 10:16:29.055 +01:00INFO__item_stack:/item1/item21
    2023-02-06 10:16:29.064 +01:00INFO__item_stack:/item4
    2023-02-06 10:16:29.095 +01:00INFO__item_stack:/item5
    2023-02-06 10:16:29.114 +01:00INFO__item_stack:/item8
    2023-02-06 10:16:29.122 +01:00INFO__item_stack:/item9
    2023-02-06 10:16:29.131 +01:00INFO__item_stack:/item9/item4
    2023-02-06 10:16:29.137 +01:00INFO__item_stack:/item9/item5
    2023-02-06 10:16:29.140 +01:00INFOSCSI controller found. (Key: 1000)
    2023-02-06 10:16:29.146 +01:00INFO__item_stack:/item9/item6
    2023-02-06 10:16:29.152 +01:00INFO__item_stack:/item9/item0
    2023-02-06 10:16:29.155 +01:00ERROR(com.vmware.library.vc.vm.spec.config.device/createVirtualDiskFlatVer2ConfigSpec) Error in (Dynamic Script Module name : createVirtualDiskFlatVer2ConfigSpec#4) TypeError: Cannot read property "info" from null
    2023-02-06 10:16:29.169 +01:00ERRORWorkflow execution stack:
    ***
    item: 'Add disk/item0', state: 'failed', business state: 'Adding disk', exception: 'TypeError: Cannot read property "info" from null (Dynamic Script Module name : createVirtualDiskFlatVer2ConfigSpec#4)'
    workflow: 'Neue VM Test Debian 11' (034d5add-8141-4a66-9272-c603d06429f4)
    | 'attribute': name=vm_user type=VC:ActionType value=
    | 'attribute': name=nic type=VC:Network value=
    | 'attribute': name=template type=boolean value=false
    | 'attribute': name=powerOn type=boolean value=false
    | 'attribute': name=doSysprep type=boolean value=true
    | 'attribute': name=vmNameOUT type=VC:VirtualMachine value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:vm-529616'&dunesName='VC:VirtualMachine'
    | 'attribute': name=dnsServerList type=Array/string value=[20:string#172.17.16.200,20:string#172.17.16.201]
    | 'attribute': name=diskMode type=VC:VirtualDiskMode value=dunes://service.dunes.ch/CustomSDKObject?id='persistent'&dunesName='VC:VirtualDiskMode'
    | 'attribute': name=disk1Index type=number value=2.0
    | 'attribute': name=disk2Index type=number value=3.0
    | 'attribute': name=thinProvisioned type=boolean value=true
    | 'attribute': name=nvmeBusNumber type=number value=2.0
    | 'input': name=clientName type=string value=t0test05
    | 'input': name=VmFolder type=VC:VmFolder value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:group-v474218'&dunesName='VC:VmFolder'
    | 'input': name=DataStore type=VC:Datastore value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:datastore-321391'&dunesName='VC:Datastore'
    | 'input': name=ResourcePool type=VC:ResourcePool value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:resgroup-213124'&dunesName='VC:ResourcePool'
    | 'input': name=vcpu type=number value=2.0
    | 'input': name=memory type=number value=8192.0
    | 'input': name=disk1Size type=number value=50.0
    | 'input': name=ipAdress type=string value=172.16.17.30
    | 'input': name=subnetmask type=string value=255.255.240.0
    | 'input': name=gateway type=Array/string value=[19:string#172.16.16.39]
    | 'input': name=AttributeZone_Value type=string value=Secure
    | 'input': name=Backup_Tag type=string value=No Backup
    | 'input': name=datastore type=VC:Datastore value=null
    | 'input': name=disk2Size type=number value=30.0
    | 'input': name=vm type=VC:VirtualMachine value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:vm-527782'&dunesName='VC:VirtualMachine'
    | 'input': name=diskAmount type=number value=1.0
    | 'input': name=network type=VC:Network value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:network-210702'&dunesName='VC:Network'
    | 'output': name=actionResult type=VC:Task value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:task-3297963'&dunesName='VC:Task'
    --workflow: 'Add disk' (BD8080808080808080808080808080801BC280800122528313869552e41805bb1)
    | 'attribute': name=scsiControllerKey type=number value=1000.0
    | 'attribute': name=task type=VC:Task value=__NULL__
    | 'attribute': name=progress type=boolean value=false
    | 'attribute': name=pollRate type=number value=1.0
    | 'attribute': name=noContollerError type=string value=Error: No controller found
    | 'input': name=vm type=VC:VirtualMachine value=dunes://service.dunes.ch/CustomSDKObject?id='svdovc01.vitodata.ch%2Cid:vm-529616'&dunesName='VC:VirtualMachine'
    | 'input': name=datastore type=VC:Datastore value=null
    | 'input': name=diskIndex type=number value=2.0
    | 'input': name=diskSize type=number value=50.0
    | 'input': name=diskMode type=VC:VirtualDiskMode value=dunes://service.dunes.ch/CustomSDKObject?id='persistent'&dunesName='VC:VirtualDiskMode'
    | 'input': name=scsiBusNumber type=number value=null
    | 'input': name=thinProvisioned type=boolean value=true
    | 'no outputs'
    *** End of execution stack.

    the Script for the task looks like this and i dont know where the problem could be:

     

    var configSpec = new VcVirtualMachineConfigSpec();
    var deviceConfigSpecs = new Array();
    var deviceConfigSpec;

    // Add/Create the disk
    deviceConfigSpec = System.getModule("com.vmware.library.vc.vm.spec.config.device").createVirtualDiskFlatVer2ConfigSpec(
        diskSize, datastore, scsiControllerKey, diskIndex, VcVirtualDiskMode.fromString(diskMode.name), thinProvisioned );
    deviceConfigSpecs[0] = deviceConfigSpec;

    // List of devices
    configSpec.deviceChange = deviceConfigSpecs;

    // Launch the reconfigVM task
    task = vm.reconfigVM_Task( configSpec );
     
    Any help would be appreciated.

     

     



  • 7.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 10, 2025 10:31 AM

    Hello, could you share which parameter was incorrect? I'm having the same issue.




  • 8.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 10, 2025 11:05 AM

    Hey, 

    please take a look here. I covered this topic in my blog post. Ping me if you will need more assistance with the disks.



    ------------------------------
    If you find the answer helpful, please click on the RECOMMEND button.

    Please visit my blog to get more information: https://www.clouddepth.com
    ------------------------------



  • 9.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 10, 2025 11:33 AM

    Thanks for the quick answer but I was referring to your initial issues => A specified parameter was not correct: spec.identity.hostName

    And I don't see that mentioned in your blog.




  • 10.  RE: A specified parameter was not correct: spec.identity.hostName

    Posted Feb 10, 2025 01:08 PM

    Sorry. My bad. I thought you have the same problem with the disk.



    ------------------------------
    If you find the answer helpful, please click on the RECOMMEND button.

    Please visit my blog to get more information: https://www.clouddepth.com
    ------------------------------