Re: Failed to copy the volume from the source primary storage pool to secondary storage

That is a known error on version 4.11.1 which has been fixed on 4.11.2 by this PR: https://github.com/apache/cloudstack/pull/2776. You can consider upgrading to version 4.11.2 to get the fix. Regards, Nicolas Vazquez From: Asai Sent: Monday, June 10, 2019

Re: Failed to copy the volume from the source primary storage pool to secondary storage

Thanks for the response, Nicolas. Here are the log entries from management-server.log corresponding to the specific time period of running the download volume command: 2019-06-10 14:00:35,893 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-86:ctx-68e69b5d job-2512) (logid:3ba6ac78)

Re: Failed to copy the volume from the source primary storage pool to secondary storage

Hi Asai, The error itself is not very descriptive but you can find more information on the logs around the failure. If you need help with it please upload it Regards, Nicolas Vazquez De: Asai Enviado: lunes, 10 de junio 18:08 Asunto: Failed to copy the volume from the source primary storage

Failed to copy the volume from the source primary storage pool to secondary storage

Greetings, I am trying to figure out the steps in migrating a KVM based guest to a Xen based guest. I have attempted to download the KVM volume so that I can attempt to attach the volume to a Xen based VM, however I get the following error when trying to download the volume: "Failed to

Re: Enabling LB service on existing zone

Hello, I don'y have a NetScale device. Can I use VR as a LB? How do I configure a basic zone with DefaultSharedNetworkOffering to allow users have LB behind their instances? Best Regards On Mon, Jun 10, 2019 at 11:37 PM Andrija Panic wrote: > Hi Fariborz, > > check here: go to Infrastcutre

Re: Enabling LB service on existing zone

Hi Fariborz, check here: go to Infrastcutre --> Zones, choose you Zone --> go to Physical networks, choose your Physical network carrying Guest traffic - and at the bottom od the page you will have "Network Service Providers". On Mon, 10 Jun 2019 at 17:40, Fariborz Navidan wrote: > Hello, > >

Re: Problem due to create network

In mgmt log you have 904 createNetwork API calls !!! Don't you think it's a bit too much ??? Check who is nailing your API, since your log looks really funny in that regards - either some automation or denial of service thing or something else (on client side) really wrong. Cheers On Mon, 10

Re: launch instance error

Interesting lines being: FirstFitRoutingAllocator) (logid:0a0b5a30) FirstFitAllocator has 1 hosts to check for allocation: [Host[-4-Routing]] 2019-06-10 13:40:11,373 DEBUG [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7 FirstFitRoutingAllocator)

Re: launch instance error

i don't know if its ok sending files over here. In case it is here is the content of the previous fail i sended root@cloudstack-manager:/home/team# grep -i "job-41" /var/log/cloudstack/management/management-server.log 2019-06-10 13:40:11,238 INFO [o.a.c.f.j.i.AsyncJobMonitor]

Re: launch instance error

Hi, thanks for your answer, as an update of mi issue i've keep digging on it and found this the log for the job. It seems like the allocation server can't find my LXC host inside the LXC cluster. I don't know anymore if my trouble is because the checksum. I attach here the file with the log output

Re: launch instance error

Hi Alejandro, Can you verify if the expected checksum is the correct and i that case update the checksum column on vm_template table fot that template and restart management server? Regards, Nicolas Vazquez From: Alejandro Ruiz Bermejo Sent: Monday, June 10,

Re: Problem due to create network

Hi Andrija, https://yadi.sk/d/BNOQFeCN86szxw - agent.log https://yadi.sk/d/5UdQ4RExJ-VfmA - management-server.log It is fresh installation with using for some days. Dmitry пн, 10 июн. 2019 г. в 17:44, Andrija Panic : > Hi Dmitry, > > if not mistaken, this might have something to do with DB -

Enabling LB service on existing zone

Hello, Is it possible to enabling LB service on an existing basic zone? Thanks

launch instance error

Hi, I'm working with Cloudstack 4.11.2.0 This is my environment: 1 Zone 1 Pod 2 Clusters (LXC and KVM) 2 Hosts (one in each cluster) i can launch perfectly VMs on the KVM cluster but when i'm trying to launch a new VM with an LXC template i'm getting this error: 2019-06-10 11:24:28,961 INFO

4.13 Heads up

In order to keep up the momentum on the release cadence, some of us are now planning to get 4.13 moving We've come up with a plan which I hope everyone will find acceptable (see below). == 4.13.0.0: (next LTS release) == * 1-5 July

K8S LoadBalancer

Hello, Does anyone has experience of using ACS as a LoadBalancer's provider for Kubernetes? As I guess, it's possible (according to these modules' presence: https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/cloudstack), but now I'm looking for some documentation

Re: Problem due to create network

Hi Dmitry, if not mistaken, this might have something to do with DB - can you please post whole log, on pastebin or similar ? Is this a fresh installation (test) or a running production for some time ? Andrija On Mon, 10 Jun 2019 at 14:55, Dmitry Berezhnoy wrote: > Hello, > > Just tried

Problem due to create network

Hello, Just tried cloudstack 4.11.2 and got the error due to create network. In cloudstack logs we got the message: "Timed out on acquiring lock account2 . Waited for 300seconds" (please read the attachment for more details). Which parameter defines this 300 seconds, where we can increase it?

Re: Unabele to boot CloudLinux on KVM after update

Fariborz, Usually indicates missing storage driver in initramfs (if you were on VMware, I would tell you to check if vmw_pvscsi.ko is present in initramfs). I've hard time believing that you might be missing initramfs completely (thought it might happen) but still would advise to re-check. If