Hi,
I am using CloudStack 4.9.2 with KVM hypervisors. Today, I find that the
hypervisor is not responding, and therefore I restart it. After that, I
find that virtual routers are stopped. When I try to start them, I keep
getting "Unable to schedule async job" error.
>From the management-se
Hi Daniel,
My initial guess without deep diving into this is your NIC naming. The
CloudStack agent looks for the interface (bond / NIC / team) which supports
cloudbr0 - and I think maybe in your case it can't find it due to the dotted
naming "eno1.8" when it probably expects some conventional l
Hello! Wanted to see if anyone else has ran into this issue or if you can
point me in the right direction...
I have 2 KVM CloudStack-agents version 4.11.2 running Centos7 that are not able
to start the cloudstack-agent service if the agent.propreties file specifies
the variable "private.networ