Hi Ron,

I did the same but made a copy of the agent properties file before hand on the 
KVM hosts.

So to roll back I restored the management server and db servers.

I then did apt-get remove cloudstack-agent cloudstack-common on the KVM host.

Finally apt-get install cloudstack-agent cloudstack-common and copied back the 
agent properties file.

The reason I know its agent related I tried starting the SSVM before rolling 
back the agent, exact same error message.  

"Secondary Storage Vm creation failure in zone [xxxx]. Error details: Unable to 
allocate capacity on zone [1] due to [null]."

After rolling back the agent it worked fine.

I spent hours going through the logs but there is nothing that stands out so 
gave up.

Thanks

Ian


    

-----Original Message-----
From: Ron Gage <r...@rongage.org.INVALID> 
Sent: 29 August 2025 15:05
To: users@cloudstack.apache.org
Subject: Re: Problem with getting SSVM running

Ian:

I wish mine was that simple.  I did a dnf remove cloudstack-agent 
cloudstack-common on the kvm host before I upgraded the agent to 4.21. I had no 
guests running on it when I went through the process.

Ron


On 8/29/25 9:51 AM, Ian Tobin wrote:
> Hi,
>
> We've also had this issue after upgrading to from 4.20.1.0 to 4.21, the SSVM 
> will not start, all pools are available.
>
> We had to roll back.  What I found is its related to the agent on the KVM 
> host but I couldn’t spend anymore time on it as the system was down.
>
> Thanks
>
> Ian
>
>      
>
> -----Original Message-----
> From: Wei ZHOU <ustcweiz...@gmail.com>
> Sent: 29 August 2025 14:48
> To: users@cloudstack.apache.org
> Subject: Re: Problem with getting SSVM running
>
> Hi,
>
> Are host and primary storage pool added ?
>
>
> -Wei
>
> On Fri, Aug 29, 2025 at 3:44 PM Ron Gage <r...@rongage.org.invalid> wrote:
>
>> Hi all!
>>
>> I'm working with a fresh install of 4.21 on Centos 9.  In a nutshell, 
>> the SSVM won't start.  Error message found in alerts: Secondary 
>> Storage Vm creation failure in zone [Mi-connect]. Error details:
>> Unable to allocate capacity on zone [1] due to [null].
>>
>> What did I do wrong now?
>>
>>
>> Ron Gage
>>

Reply via email to