Hi Alex, I'm unfamiliar with Xen, but can you check if the template `44b911df-3138-414b-9604-e7254372ad9b` exists in your primary storage? On every first deployment of a VM with a new template, CS copies the template from secondary storage to the primary. The template may be missing on primary (for some reason) but CloudStack keeps the info for the record in the database and tries to create a volume from it.
Best regards, Slavka On Thu, Feb 29, 2024 at 8:49 AM Joan g <[email protected]> wrote: > Hi Wei, > > Storage also does not have any tags. Attaching logs > > Alex > > On Thu, Feb 29, 2024 at 12:09 AM Wei ZHOU <[email protected]> wrote: > >> Hi Alex, >> >> The tags are the disk offering tags. >> >> Anyway , can you share the full log of the job ? >> >> -Wei >> >> On Wed, Feb 28, 2024 at 6:47 PM Alex Paul <[email protected]> >> wrote: >> >> > Hi Wei, >> > >> > No tags are there. I think in logs also its not printing to any tags: >> > >> > >> > Found pools [[Pool[1|PreSetup]]] that match with tags [[]]. >> > >> > The VM deployments were fine 2 days before. All in a sudden it started >> > failing. >> > >> > >> > Alex >> > >> > On Wednesday, February 28, 2024, Wei ZHOU <[email protected]> >> wrote: >> > >> > > Agree. >> > > >> > > Please also check if the pool has any tags. >> > > >> > > -Wei >> > > >> > > On Wed, Feb 28, 2024 at 5:31 PM Slavka Peleva >> > <[email protected] >> > > > >> > > wrote: >> > > >> > > > Hi Alex, >> > > > >> > > > Sorry for the question but is it possible that the cluster is >> > disabled? I >> > > > have faced a similar problem before while testing. >> > > > >> > > > Best regards, >> > > > Slavka >> > > > >> > > > On Wed, Feb 28, 2024 at 5:15 PM Alex Paul < >> [email protected] >> > > >> > > > wrote: >> > > > >> > > > > Hi Swen, >> > > > > >> > > > > Yes, only 3TB used out of 15TB and double checked the threshold >> is at >> > > > 85%. >> > > > > :( >> > > > > >> > > > > Alex >> > > > > >> > > > > On Wed, Feb 28, 2024 at 7:32 PM <[email protected]> wrote: >> > > > > >> > > > > > Hi Alex, >> > > > > > >> > > > > > is there enough free space on the storage? Check your >> thresholds in >> > > > > global >> > > > > > settings. >> > > > > > >> > > > > > Regards, >> > > > > > Swen >> > > > > > >> > > > > > -----Ursprüngliche Nachricht----- >> > > > > > Von: Alex Paul <[email protected]> >> > > > > > Gesendet: Mittwoch, 28. Februar 2024 14:24 >> > > > > > An: [email protected] >> > > > > > Betreff: Storage in avoid set >> > > > > > >> > > > > > Hello Team, >> > > > > > >> > > > > > We've encountered an issue with our cloudstack setup on 3 XCP-ng >> > > hosts. >> > > > > > Suddenly, VM deployments are failing. >> > > > > > >> > > > > > Our configuration includes a primary storage of type 'presetup' >> > using >> > > > > HBA. >> > > > > > Interestingly, the storage functions properly in the XEN >> cluster, >> > > > > allowing >> > > > > > us to deploy VMs directly in xen. >> > > > > > >> > > > > > However, in cloudstack, deployments are failing with the >> following >> > > > logs: >> > > > > > "StoragePool is in avoid set, skipping this pool." >> > > > > > >> > > > > > Could someone please provide guidance on why it's in the avoid >> set >> > > and >> > > > > how >> > > > > > we can remove it from there? >> > > > > > >> > > > > > Full logs are provided below for reference. >> > > > > > >> > > > > > >> > > > > > 024-02-27 11:24:04,879 DEBUG >> > > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> > > > > > ctx-02929e21) (logid:97976fdd) Looking for pools in dc [1], pod >> > [1] >> > > > and >> > > > > > cluster [1]. Disabled pools will be ignored. >> > > > > > 2024-02-27 11:24:04,881 DEBUG >> > > > > [o.a.c.s.a.ClusterScopeStoragePoolAllocator] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> > > > > > ctx-02929e21) (logid:97976fdd) Found pools [[Pool[1|PreSetup]]] >> > that >> > > > > > match with tags [[]]. >> > > > > > 2024-02-27 11:24:04,885 DEBUG [o.a.c.s.a. >> > > AbstractStoragePoolAllocator] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 ctx >> > > > > > -02929e21) (logid:97976fdd) Checking if storage pool is >> suitable, >> > > name: >> > > > > > CLOUDSTACKVOL1 ,poolId: 1 >> > > > > > 2024-02-27 11:24:04,885 DEBUG [o.a.c.s.a. >> > > AbstractStoragePoolAllocator] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) StoragePool is in avoid set, skipping this pool >> > > > > > 2024-02-27 11:24:04,885 DEBUG [o.a.c.s.a. >> > > AbstractStoragePoolAllocator] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) ClusterScopeStoragePoolAllocator is returning >> [0] >> > > > > > suitable storage pools [[]]. >> > > > > > 2024-02-27 11:24:04,891 DEBUG [o.a.c.s.a. >> > > AbstractStoragePoolAllocator] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) ZoneWideStoragePoolAllocator is returning [0] >> > > suitable >> > > > > > storage pools [[]]. >> > > > > > 2024-02-27 11:24:04,891 DEBUG >> [c.c.d.DeploymentPlanningManagerImpl] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) No suitable pools found for volume: >> > > > > > Vol[1182|name=ROOT-1133|vm=1133|ROOT] under cluster: 1 >> > > > > > 2024-02-27 11:24:04,891 DEBUG >> [c.c.d.DeploymentPlanningManagerImpl] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) No suitable pools found >> > > > > > 2024-02-27 11:24:04,891 DEBUG >> [c.c.d.DeploymentPlanningManagerImpl] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) No suitable storagePools found under this >> > Cluster: 1 >> > > > > > 2024-02-27 11:24:04,898 DEBUG >> [c.c.d.DeploymentPlanningManagerImpl] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) Could not find suitable Deployment Destination >> for >> > > > this >> > > > > > VM under any clusters, returning. >> > > > > > 2024-02-27 11:24:04,900 DEBUG [c.c.d.FirstFitPlanner] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) Searching all possible resources under this >> Zone: >> > 1 >> > > > > > 2024-02-27 11:24:04,903 DEBUG [c.c.d.FirstFitPlanner] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) Listing clusters in order of aggregate >> capacity, >> > > that >> > > > > > have (at least one host with) enough CPU and RAM capacity under >> > this >> > > > > Zone: 1 >> > > > > > 2024-02-27 11:24:04,910 DEBUG [c.c.d.FirstFitPlanner] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) Removing from the clusterId list these clusters >> > from >> > > > > avoid >> > > > > > set: [1] >> > > > > > 2024-02-27 11:24:04,911 DEBUG [c.c.d.FirstFitPlanner] >> > > > > > (Work-Job-Executor-1:ctx-5ab127f5 job-12670/job-12671 >> ctx-02929e21) >> > > > > > (logid:97976fdd) No clusters found after removing disabled >> clusters >> > > and >> > > > > > clusters in avoid list, returning. >> > > > > > >> > > > > > >> > > > > > >> > > > > > Alexi >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >> >
