Hi Bernardo,

It was indeed the lack of affinity group selection that did the trick.
I wasn't aware that upon dedication of resources, this would be necessary
but this seems to work now.

Thanks!

Jeroen Kleijer

On Fri, Dec 6, 2024 at 12:34 PM Bernardo De Marco Gonçalves <
bernardomg2...@gmail.com> wrote:

> Hello, Jeroen
>
> In CloudStack, when an infrastructure resource (such as a host, cluster,
> pod, or zone) is dedicated to an account or domain, an affinity group of
> the "ExplicitDedication" type is automatically created.
>
> As a result, when deploying a VM intended to run on a dedicated resource,
> it is necessary to select the "Advanced Mode" toggle in the VM wizard form
> and select the affinity group associated with the resource dedication. This
> is likely the reason for the VM deployment failure in the described
> scenario. Selecting the affinity group should resolve the issue.
>
> Best regards,
> Bernardo De Marco Gonçalves (bernardodemarco)
>
> Em sex., 6 de dez. de 2024 às 06:57, Jeroen Kleijer <
> jeroen.klei...@gmail.com> escreveu:
>
> > 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
> >
>

Reply via email to