DaanHoogland commented on issue #5803: URL: https://github.com/apache/cloudstack/issues/5803#issuecomment-1010894271
@edikevich , Are you expecting the dedicated POD to be automatically choosen? this line says there is no POD chosen: ``` 2022-01-12 12:42:14,433 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Trying to allocate a host and storage pools from dc:1, pod:null,cluster:null, requested cpu: 2000, requested ram: (2.00 GB) 2147483648 ``` Are there any not-dedicated PODs in your environment? the following line says there are 2 POD that will be avoided. ``` 2022-01-12 12:42:14,441 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Deploy avoids pods: [2], clusters: [], hosts: [] ``` the decision to not deploy is at the cluster level: ``` 2022-01-12 12:42:14,444 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Listing clusters in order of aggregate capacity, that have (at least one host with) enough CPU and RAM capacity under this Zone: 1 2022-01-12 12:42:14,448 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) Removing from the clusterId list these clusters from avoid set: [] 2022-01-12 12:42:14,454 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) The clusterId list for the given offering tag: [] 2022-01-12 12:42:14,454 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) No clusters found after removing disabled clusters and clusters in avoid list, returning. ``` It looks like there is a tag on the offering that none of the (1) cluster(s) has so there is a mismatch in tags. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
