Hi Sangwoo,

Do you have NFS server running on your desktop/laptop (i.e. 172.20.0.1?) and 
are the firewall rules relaxes to allow the related ports.

Please refer to 
https://github.com/shapeblue/hackerbook/blob/master/2-dev.md#setup-nfs-storage 
on setting up NFS storage and ensure that you've exported the shares (i.e. via 
the /etc/exports and calling exportfs -a). Next, I would advise that you 
manually try to mount a test folder inside one of your mgmt server or kvm hosts 
(assuming you're using mbx/monkeyboxes).


Regards.

________________________________
From: Andrija Panic <andrija.pa...@gmail.com>
Sent: Wednesday, June 9, 2021 04:45
To: dev <dev@cloudstack.apache.org>
Subject: Re: Problems while deploying Datacenter

If I were to read the logs at all, I would have found the lines which says:

Child process (/usr/bin/mount
172.20.0.1:/export/testing/qa1-cloudstack-testdrive-8167a357-kvm/primary1
/mnt/46ae40e1-4b14-30b9-b0d3-446ae7c4829d -o nodev,nosuid,noexec)
unexpected exit status 32: mount.nfs: Connection timed out

...meaning your host could not mount the NFS - i.e. go and manually try to
mount it, with the given parameters - and see if you can - the answer is
probably "no, can't mount it" - then investigate and ensure a manual mount
is working fine (firewall, nfs down, NFS access list, etc) - then come back
to ACS and it will magically work ;)


Best,

On Tue, 8 Jun 2021 at 19:21, Sangwoo Bae
<baesangwo...@googlemail.com.invalid> wrote:

> This is the part of the management server logs, where it timed out:
>
>
> 2021-06-08 13:26:53,442 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-8:null) (logid:) Seq 2-5273715163650850829:
> Processing:  { Ans: , MgmtId: 90520743956645, via: 2, Ver: v1, Flags: 10,
>
> [{"com.cloud.agent.api.Answer":{"result":"false","details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount
> 172.20.0.1:/export/testing/qa1-cloudstack-testdrive-8167a357-kvm/primary1
> /mnt/46ae40e1-4b14-30b9-b0d3-446ae7c4829d -o nodev,nosuid,noexec)
> unexpected exit status 32: mount.nfs: Connection timed out
>
> at
>
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:624)
> at
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:330)
> at
>
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:324)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtModifyStoragePoolCommandWrapper.execute(LibvirtModifyStoragePoolCommandWrapper.java:42)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtModifyStoragePoolCommandWrapper.execute(LibvirtModifyStoragePoolCommandWrapper.java:35)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
> at
>
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1667)
> 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 java.base/java.lang.Thread.run(Thread.java:829)
> ","wait":"0","bypassHostMaintenance":"false"}}] }
>
> On Tue, 8 Jun 2021 at 19:15, Sangwoo Bae <baesangwo...@googlemail.com>
> wrote:
>
> > Hi all,
> >
> > I have been trying to set up a cloudstack environment, and during the
> > setup of the deployment of the datacenters marvin threw an exception:
> >
> > createstoragepool failed, due to: errorCode: 530, errorText:Failed to add
> > data store: Failed to access storage pool
> >
> > I would really appreciate help.
> >
> > Thanks in advance,
> > Sangwoo
> >
>


--

Andrija Panić

 

Reply via email to