-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect arguments passed to instance placement scriptlet on instance move #1299
Comments
Things actually seem consistent here, just not particularly ideal:
and then:
I don't know why in your case you're only seeing the Basically during the move, Incus uses the Then after that decision is made, Incus internally handles the cross-project move which effectively is a copy+delete, that's why we get the |
Now ideally we'd be able to:
I'll take a look into this now. The project name part should be pretty trivial, eliminating the |
Closes lxc#1299 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes lxc#1299 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes lxc#1299 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes lxc#1299 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Thank you very much, when I have the time, I'll update and test everything out and report of I find anything odd. |
Closes #1299 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
When
incus move
is used to move an instance between projects in a cluster, the arguments used to call the placement scriptlet are incorrect.I have 3 projects with the following cluster group restrictions.
And the following cluster groups.
I have a scriptlet with the following part for logging the input.
So I create and instance on project auxiliar and use
incus move
to move it between all possible pairs of projects, I get the following sequence of command and log. So the set of candidate members always includes just one node instead of the full cluster group. Furthermore, sometimes the target project is incorrect, like when moving from amd-5700g to auxiliar, which is quite awkward.The text was updated successfully, but these errors were encountered: