HI

in KVM  host ,

virsh pool-list


it did not show primary storage that is enabled in GUI


 the storage is healthy in GUI, but virsh pool-list does not show .

Agent Log:

2023-08-22 19:30:34,067 INFO  [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-1:null) (logid:ad31d0e2) Trying to fetch storage pool
bfb5965d-b463-3111-84a2-3f1609ffe81a from libvirt



MGMT Log:


2023-08-23 03:43:05,926 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-7:null) (logid:) Seq 22-6027223676305325212:
Processing:  { Ans: , MgmtId: 132241052848475, via: 22, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":"false","details":"com.cloud.utils.exception.CloudRuntimeException:
com.cloud.utils.exception.CloudRuntimeException: Could not fetch storage
pool bfb5965d-b463-3111-84a2-3f1609ffe81a from libvirt

at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getPhysicalDisk(KVMStoragePoolManager.java:314)

at
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtDeleteVMSnapshotCommandWrapper.execute(LibvirtDeleteVMSnapshotCommandWrapper.java:97)

at
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtDeleteVMSnapshotCommandWrapper.execute(LibvirtDeleteVMSnapshotCommandWrapper.java:43)

at
com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)

at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1648)

at com.cloud.agent.Agent.processRequest(Agent.java:661)

at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1079)

at com.cloud.utils.nio.Task.call(Task.java:83)

at com.cloud.utils.nio.Task.call(Task.java:29)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at






CLoudstack Version : 4.15 , on Ubuntu 18/20



And thus the VM disk inside is not able to start


Any one have experience to solve this




-- 
Regards,
Hean Seng

Reply via email to