Hi, Did you deploy the VMs in projects or in the default view (account view) ?
The cloudstack project uses a different account from the account/user logged in. If you deploy a VM in a project, you need to dedicate the cluster to the project, not the account logged in. -Wei On Fri, Dec 6, 2024 at 10:58 AM Jeroen Kleijer <jeroen.klei...@gmail.com> wrote: > Hi all, > > I've created an ACS setup where we have different accounts, setup projects > matching those accounts and created several different clusters. > We have three clusters each dedicated to a different account. > > If I now try to create a VM, it will fail with the message: > No destination found for a deployment for VM instance.... > > If I go to the ACS Management logs, I notice the following: > Deploy avoids pods: [], clusters: [19, 22, 25], hosts: [] > > Those three IDs are the IDs of my clusters. > > If I now release a particular cluster, and try to deploy a VM again, it > will succeed. Looking at the corresponding log messages, I notice the > following: > Deploy avoids pods: [], clusters: [22, 25], hosts: [] > > So then it is able to deploy a VM. > > The strange thing is... this deployment of VMs fails as both the "admin" > account as well as a user account that belongs to the ACS Account to which > the cluster is dedicated. > > So my question basically boils down to this: > - is my understanding of how the "dedicated" feature is supposed to work, > correct? (if not, then please enlighten me :) ) > - if it is correct, are we hitting a bug or something? > > Kind regards, > > Jeroen Kleijer >
