top-secrett commented on issue #7536:
URL: https://github.com/apache/cloudstack/issues/7536#issuecomment-1603974119

   @DaanHoogland Sorry for delay. Steps by @harikrishna-patnala are correct.
   I've tested it again on test CS server and I couldn't find any "Detected 
disk-chain top file change on volume" records. 
   
   Test CS server:
   ~~~
   2023-06-23 04:11:02,929 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) Looking for disk device info for volume 
[87d3b809200c4341884f03f12077deba.vmdk] with base name 
[87d3b809200c4341884f03f12077deba].
   2023-06-23 04:11:02,929 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) Testing if disk device with controller key 
[1000] and unit number [0] has backing of type VirtualDiskFlatVer2BackingInfo.
   2023-06-23 04:11:02,930 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) Testing if backing datastore name [SAS-500] from 
backing [[SAS-500] i-2-139-VM/i-2-139-VM.vmdk] matches source datastore name [].
   2023-06-23 04:11:02,930 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) No disk device exactly matching 
[87d3b809200c4341884f03f12077deba] was found for volume 
[87d3b809200c4341884f03f12077deba.vmdk]. Looking for disk device info against 
trimmed base name [87d3b809200c4341884f03f12077deba].
   2023-06-23 04:11:02,930 WARN  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) Disk device info lookup for volume 
[87d3b809200c4341884f03f12077deba.vmdk] failed as no matching disk device was 
found.
   2023-06-23 04:11:02,930 INFO  [c.c.h.v.u.VmwareHelper] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) [ignored]failed to get message for exception: No 
such disk device: 87d3b809200c4341884f03f12077deba.vmdk
   2023-06-23 04:11:02,930 ERROR [c.c.h.v.r.VmwareResource] 
(DirectAgent-472:ctx-1eb3cc22 10.69.83.133, job-1324/job-1326, cmd: 
StartCommand) (logid:992fc8d6) StartCommand failed due to [Exception: 
java.lang.Exception
   Message: No such disk device: 87d3b809200c4341884f03f12077deba.vmdk
   ].
   java.lang.Exception: No such disk device: 
87d3b809200c4341884f03f12077deba.vmdk
           at 
com.cloud.hypervisor.vmware.resource.VmwareResource.getVirtualDiskInfo(VmwareResource.java:5073)
           at 
com.cloud.hypervisor.vmware.resource.VmwareResource.resizeRootDiskOnVMStart(VmwareResource.java:3049)
           at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2612)
           at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:564)
           at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
           at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
           at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
           at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
           at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
           at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
           at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
           at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
           at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
           at java.base/java.lang.Thread.run(Thread.java:829)
   ~~~
   
   But in prodiction CS I found "Detected disk-chain top file change on volume" 
record
   ~~~
   ISO volume at existing device {"key":3000,"deviceInfo":{"label":"CD/DVD 
drive 1","summary":"ISO [752cae7b2f803c6886040e5512ba017b] 
template/tmpl/2/204/204-2-ad799b3e-0d1e-3e4b-9f04-048d04b71833.iso"},"backing":{"fileName":"[752cae7b2f803c6886040e5512ba017b]
 
template/tmpl/2/204/204-2-ad799b3e-0d1e-3e4b-9f04-048d04b71833.iso","datastore":{"value":"datastore-388","type":"Datastore"}},"connectable":{"startConnected":true,"allowGuestControl":false,"connected":true},"controllerKey":200,"unitNumber":0}
   2023-06-23 12:00:51,576 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Found existing disk from from chain device 
bus information: scsi0:0
   2023-06-23 12:00:51,576 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Chose disk controller for vol ROOT -> 
lsilogic, based on root disk controller settings at global configuration 
setting.
   2023-06-23 12:00:51,581 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Detected disk-chain top file change on 
volume: 3559 5c4f07b509d54be8957793bf25bd6e8d -> i-60-3387-VM
   2023-06-23 12:00:51,586 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Found existing disk info from volume path: 
i-60-3387-VM
   2023-06-23 12:00:51,597 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Detected datastore uuid change on volume: 
3559 aeb66841-98b1-3dff-bb31-c1035474ee95 -> 
18d752de-1afa-3431-a990-726404774e05
   2023-06-23 12:00:51,606 DEBUG [c.c.u.LogUtils] (DirectAgent-140:ctx-c01e36d5 
esx-sr184-u1112.aisrp.local, job-41159/job-41161, cmd: StartCommand) 
(logid:8ffe3c3a) Failed to log object [VirtualMachineMO] using GSON.
   2023-06-23 12:00:51,607 DEBUG [c.c.h.v.u.VmwareHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Trying to prepare disk device to virtual 
machine [error to decode], using the following details: Virtual device [], 
ManagedObjectReference [{"value":"datastore-342","type":"Datastore"}], 
ControllerKey [1000], VMDK path chain [["[ds-sr183_185_os5500-sas-1] 
i-60-3387-VM/i-60-3387-VM.vmdk"]], DeviceNumber [0], ContextNumber [2] and max 
IOPS [0].
   2023-06-23 12:00:51,612 DEBUG [c.c.u.LogUtils] (DirectAgent-140:ctx-c01e36d5 
esx-sr184-u1112.aisrp.local, job-41159/job-41161, cmd: StartCommand) 
(logid:8ffe3c3a) Failed to log object [VirtualMachineMO] using GSON.
   2023-06-23 12:00:51,612 DEBUG [c.c.h.v.u.VmwareHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Prepared disk device, to attach to virtual 
machine [error to decode], has the following details: Virtual device [], 
ManagedObjectReference [{"value":"datastore-342","type":"Datastore"}], 
ControllerKey [1000], VMDK path chain [["[ds-sr183_185_os5500-sas-1] 
i-60-3387-VM/i-60-3387-VM.vmdk"]], DeviceNumber [0], ContextNumber [2] and max 
IOPS [0], is: 
[{"capacityInKB":0,"key":-2,"backing":{"diskMode":"persistent","fileName":"[ds-sr183_185_os5500-sas-1]
 
i-60-3387-VM/i-60-3387-VM.vmdk","datastore":{"value":"datastore-342","type":"Datastore"}},"connectable":{"startConnected":true,"allowGuestControl":false,"connected":true},"controllerKey":1000,"unitNumber":0}].
   2023-06-23 12:00:51,612 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) The following definitions will be used to 
start the VM: virtual device 
[{"capacityInKB":0,"key":-2,"backing":{"diskMode":"persistent","fileName":"[ds-sr183_185_os5500-sas-1]
 
i-60-3387-VM/i-60-3387-VM.vmdk","datastore":{"value":"datastore-342","type":"Datastore"}},"connectable":{"startConnected":true,"allowGuestControl":false,"connected":true},"controllerKey":1000,"unitNumber":0}],
 volume 
[{"uuid":"35d68a62-f5a2-4a2d-a8a7-d789a9b67514","volumeType":"ROOT","dataStore":{"uuid":"18d752de-1afa-3431-a990-726404774e05","name":"ds-sr183_185_os5500-nlsas-1","id":35,"poolType":"PreSetup","host":"vcsa-cs.aisrp.local","path":"/dc1/ds-sr183_185_os5500-nlsas-1","port":0,"url":"PreSetup://vcsa-cs.aisrp.local/dc1/ds-sr183_185_os5500-nlsas-1/?ROLE\u003dPrimary\u0026STOREUUID\u003daeb66841-98b1-3dff-bb31-c1035474ee95","isManaged
 
":false,"parentPoolType":"DatastoreCluster"},"name":"ROOT-3387","size":10737418240,"path":"i-60-3387-VM","volumeId":3559,"vmName":"i-60-3387-VM","accountId":60,"chainInfo":"{\"diskDeviceBusName\":\"scsi0:0\",\"diskChain\":[\"[ds-sr183_185_os5500-nlsas-1]
 
i-60-3387-VM/5c4f07b509d54be8957793bf25bd6e8d.vmdk\"]}","format":"OVA","provisioningType":"THIN","poolId":35,"id":3559,"deviceId":0,"bytesReadRate":0,"bytesWriteRate":0,"iopsReadRate":0,"iopsWriteRate":0,"cacheMode":"NONE","hypervisorType":"VMware","directDownload":false,"deployAsIs":false,"passphrase":[]}].
   2023-06-23 12:00:51,612 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Prepare volume at new device 
{"capacityInKB":0,"key":-2,"backing":{"diskMode":"persistent","fileName":"[ds-sr183_185_os5500-sas-1]
 
i-60-3387-VM/i-60-3387-VM.vmdk","datastore":{"value":"datastore-342","type":"Datastore"}},"connectable":{"startConnected":true,"allowGuestControl":false,"connected":true},"controllerKey":1000,"unitNumber":0}
   2023-06-23 12:00:51,612 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Prepare NIC device based on NicTO: 
{"deviceId":0,"networkRateMbps":10000,"defaultNic":true,"pxeDisable":false,"nicUuid":"ab38456e-4f11-4fb8-8a52-3e348ffe94ae","details":{"MacLearning":"false","internetProtocol":"IPv4","PromiscuousMode":"false","MacAddressChanges":"true","ForgedTransmits":"true"},"dpdkEnabled":false,"uuid":"d4152505-c430-43b1-ba14-31ab9257c73b","ip":"10.1.2.155","netmask":"255.255.255.0","gateway":"10.1.2.1","mac":"02:00:67:57:00:97","dns1":"93.125.22.110","dns2":"93.125.22.108","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://2118","isolationUri":"vlan://2118","isSecurityGroupEnabled":false,"name":"dsw-clusters_1-2,2100-2300,vmwaredvs"}
   2023-06-23 12:00:51,612 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) VM i-60-3387-VM will be started with NIC 
device type: E1000 on NIC device 0
   2023-06-23 12:00:51,617 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Prepare network on vmwaredvs 
dsw-clusters_1-2 with name prefix: cloud.guest
   2023-06-23 12:00:51,639 DEBUG [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Found distributed vSwitch: dsw-clusters_1-2 
with product version: 6.6.0
   2023-06-23 12:00:51,639 DEBUG [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Creating dvSwitch port vlan-id spec with 
id: 2118
   2023-06-23 12:00:51,646 INFO  [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Found Distributed Virtual Port group 
cloud.guest.2118.10000.1-dsw-clusters_1-2
   2023-06-23 12:00:51,674 DEBUG [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Checking if configuration of dvPortGroup 
[cloud.guest.2118.10000.1-dsw-clusters_1-2] has changed.
   2023-06-23 12:00:51,692 DEBUG [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Added custom field : cloud.gc.dvp
   2023-06-23 12:00:51,712 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Preparing NIC device on dvSwitch : 50 0c d1 
70 9e a8 33 cf-6d 43 db 29 a9 fd c1 8e
   2023-06-23 12:00:51,713 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Prepare NIC at new device 
{"operation":"ADD","device":{"addressType":"Manual","macAddress":"02:00:67:57:00:97","key":-3,"backing":{"port":{"switchUuid":"50
 0c d1 70 9e a8 33 cf-6d 43 db 29 a9 fd c1 
8e","portgroupKey":"dvportgroup-622"}},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true}}}
   2023-06-23 12:00:51,713 DEBUG [c.c.h.v.m.HostMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) find VM i-60-3387-VM on host
   2023-06-23 12:00:51,713 DEBUG [c.c.h.v.m.HostMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) VM i-60-3387-VM found in host cache
   2023-06-23 12:00:51,762 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Configure VNC port for VM i-60-3387-VM, 
port: 5907, host: esx-sr184-u1112.aisrp.local
   2023-06-23 12:00:53,418 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Looking for disk device info for volume 
[5c4f07b509d54be8957793bf25bd6e8d.vmdk] with base name 
[5c4f07b509d54be8957793bf25bd6e8d].
   2023-06-23 12:00:53,418 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Testing if disk device with controller key 
[1000] and unit number [0] has backing of type VirtualDiskFlatVer2BackingInfo.
   2023-06-23 12:00:53,418 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Testing if backing datastore name 
[ds-sr183_185_os5500-sas-1] from backing [[ds-sr183_185_os5500-sas-1] 
i-60-3387-VM/i-60-3387-VM.vmdk] matches source datastore name [].
   2023-06-23 12:00:53,418 INFO  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) No disk device exactly matching 
[5c4f07b509d54be8957793bf25bd6e8d] was found for volume 
[5c4f07b509d54be8957793bf25bd6e8d.vmdk]. Looking for disk device info against 
trimmed base name [5c4f07b509d54be8957793bf25bd6e8d].
   2023-06-23 12:00:53,418 WARN  [c.c.h.v.m.VirtualMachineMO] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) Disk device info lookup for volume 
[5c4f07b509d54be8957793bf25bd6e8d.vmdk] failed as no matching disk device was 
found.
   2023-06-23 12:00:53,418 INFO  [c.c.h.v.u.VmwareHelper] 
(DirectAgent-140:ctx-c01e36d5 esx-sr184-u1112.aisrp.local, job-41159/job-41161, 
cmd: StartCommand) (logid:8ffe3c3a) [ignored]failed to get message for 
exception: No such disk device: 5c4f07b509d54be8957793bf25bd6e8d.vmdk
   
   ~~~
   
   
   But I don't understand why does CS use disk names different from VM names?


-- 
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