Hi Dag,
We were getting below logs from management server.
2016-11-09 21:36:53,096 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-4:null) Seq 1-4251679523214458881: Processing: {
Ans: , MgmtId: 207381009036, via: 1, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.ModifyStoragePoolAnswer":{"p
Hi Dag,
We had mounted the NFS share on management server before executed the
script. Also there was no /secondary or other local directory on our
management server. All that presented is NFS secondary share.
Can we change any global settings or alter cloud DB entries for the
working of thi
Hi Kurt,
As Simon is hinting at it looks like you didn’t mount the secondary storage NFS
share on your management server before running:
"/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /secondary -u
http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4
Hi Simon,
Thanks for the response.
>> Is your secondary storage on a separate NFS server?
Yeah, we have used separate NFS server.
>> Have you added the secondary storage mount to CloudStack Management?
We had tried this. But no luck.
===
162.x.x.x:/export/secondary nfs 913G 2.0G 865G 1% /m
We run into this "problem" too. Here are my 2 cents:
API call should respect affinity groups, but it should be able for
administrator to force a migration (force=true).
As an administrator you cannot control (or have in mind) all affinity groups
when you need to evacuate a host. At the moment yo
