Hi Wei, I just patched 4.21.0 with https://github.com/apache/cloudstack/pull/11557 , it works as expected. Thank you very much.
Regards, Levin On 6 Sep 2025 at 02:06 +0800, Wei ZHOU <[email protected]>, wrote: > Hi, > > The issue has been reported: > https://github.com/apache/cloudstack/issues/11552 > > Please keep eye on the issue > > > -Wei > > > > On Fri, Sep 5, 2025 at 7:22 PM Levin Ng <[email protected]> wrote: > > > Hi all, > > > > > > I got problem with SSVM as well, after upgrade from 4.20.1 to 4.21.0, > > while rolling the system vm, I got this error from agent, no clue after an > > hour troubleshooting > > > > 2025-09-06 01:08:38,689 WARN [cloud.agent.Agent] > > (AgentRequest-Handler-2:[]) (logid:dcb78e11) Caught: > > java.lang.NullPointerException > > at > > com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:180) > > at > > com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:234) > > at > > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:258) > > at > > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3816) > > at > > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3395) > > at > > com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:86) > > at > > com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:52) > > at > > com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78) > > at > > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:2240) > > at com.cloud.agent.Agent.processRequest(Agent.java:813) > > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1295) > > 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) > > > > Regards, > > Levin > > On 29 Aug 2025 at 22:16 +0800, Ian Tobin <[email protected]>, > > wrote: > > > 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 <[email protected]> > > > Sent: 29 August 2025 15:05 > > > To: [email protected] > > > 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 <[email protected]> > > > > Sent: 29 August 2025 14:48 > > > > To: [email protected] > > > > 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 <[email protected]> > > 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 > > > > > > > > > >
