shwstppr commented on PR #8492:
URL: https://github.com/apache/cloudstack/pull/8492#issuecomment-1887036684

   @nvazquez @DaanHoogland I retested case#9 from 
https://github.com/apache/cloudstack/pull/8492#issuecomment-1886874307 and it 
is failing as expected, therefore it all looks good on VMware side
   
   ```
   (localcloud) 🐱 > list vlanipranges id=3f69aecb-1aae-4f7e-b559-1e5c9eeac568 
   {
     "count": 1,
     "vlaniprange": [
       {
         "account": "system",
         "cidr": "10.8.0.0/24",
         "domain": "ROOT",
         "domainid": "a2138f1e-af98-11ee-847d-1e0058000a5d",
         "endip": "10.8.0.200",
         "forsystemvms": false,
         "forvirtualnetwork": false,
         "gateway": "10.8.0.1",
         "id": "3f69aecb-1aae-4f7e-b559-1e5c9eeac568",
         "netmask": "255.255.255.0",
         "networkid": "587d654e-fee0-49ab-a736-925e24d684c9",
         "physicalnetworkid": "c654f1ef-6047-4cd8-882b-f407dc604c4c",
         "startip": "10.8.0.101",
         "vlan": "2121",
         "zoneid": "b4a732bb-e837-4682-bbb9-b845b04a17dd"
       }
     ]
   }
   (localcloud) 🐱 > list unmanagedinstances 
clusterid=e3087b2f-8be7-4832-b8ef-61d7e25b27cf name=i-2-30-VM
   {
     "count": 1,
     "unmanagedinstance": [
       {
         "clusterid": "e3087b2f-8be7-4832-b8ef-61d7e25b27cf",
         "clustername": "p1-c1",
         "cpucorepersocket": 1,
         "cpunumber": 1,
         "cpuspeed": 0,
         "disk": [
           {
             "capacity": 52428800,
             "controller": "lsilogic",
             "controllerunit": 0,
             "datastorehost": "10.1.32.4",
             "datastorename": "5b2964142196369d96d6b95b6ad5e170",
             "datastorepath": 
"/acs/primary/ref-trl-5272-v-Mr8-abhishek-kumar/ref-trl-5272-v-Mr8-abhishek-kumar-esxi-pri1",
             "datastoretype": "NFS",
             "id": "15-2000",
             "imagepath": "[5b2964142196369d96d6b95b6ad5e170] 
i-2-30-VM/ROOT-30.vmdk",
             "label": "Hard disk 1",
             "position": 0
           }
         ],
         "hostid": "d178e42e-1c2e-452b-a572-eac1fd2fb11c",
         "hostname": "10.1.32.206",
         "memory": 512,
         "name": "i-2-30-VM",
         "nic": [
           {
             "adaptertype": "E1000",
             "id": "Network adapter 1",
             "macaddress": "02:01:00:cc:00:0d",
             "networkname": "cloud.guest.1747.200.1-vSwitch1",
             "vlanid": 1747
           }
         ],
         "osdisplayname": "Other Linux (64-bit)",
         "osid": "otherLinux64Guest",
         "powerstate": "PowerOn"
       }
     ]
   }
   (localcloud) 🐱 > import unmanagedinstance name=i-2-30-VM 
clusterid=e3087b2f-8be7-4832-b8ef-61d7e25b27cf displayname=erwewr 
zoneid=b4a732bb-e837-4682-bbb9-b845b04a17dd importsource=unmanaged 
hypervisor=vmware serviceofferingid=cec984be-1c57-468b-b1b1-94ea3cef705e 
nicnetworklist[0].nic=Network adapter 1 
nicnetworklist[0].network=51978449-5557-41f7-8642-35739fcc90ae 
nicipaddresslist[0].nic="Network adapter 1" 
nicipaddresslist[0].ip4Address=10.8.0.52
   {
     "account": "admin",
     "accountid": "c77ca2f3-af98-11ee-847d-1e0058000a5d",
     "cmd": 
"org.apache.cloudstack.api.command.admin.vm.ImportUnmanagedInstanceCmd",
     "completed": "2024-01-11T12:13:36+0000",
     "created": "2024-01-11T12:13:36+0000",
     "domainid": "a2138f1e-af98-11ee-847d-1e0058000a5d",
     "domainpath": "ROOT",
     "jobid": "2c50b7a2-fe40-4705-8fbd-be08eba1bf54",
     "jobprocstatus": 0,
     "jobresult": {
       "errorcode": 530,
       "errortext": "IP address 10.8.0.52 for NIC(ID: Network adapter 1) is not 
available in network(ID: 51978449-5557-41f7-8642-35739fcc90ae)"
     },
     "jobresultcode": 530,
     "jobresulttype": "object",
     "jobstatus": 2,
     "userid": "c77dbaa7-af98-11ee-847d-1e0058000a5d"
   }
   🙈 Error: async API failed for job 2c50b7a2-fe40-4705-8fbd-be08eba1bf54
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to