-
Notifications
You must be signed in to change notification settings - Fork 930
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
Tiny fixes #12143
Tiny fixes #12143
Conversation
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
https://github.com/canonical/lxd/actions/runs/5825820485/job/15798320627?pr=12143:
In |
Signed-off-by: Simon Deziel <simon.deziel@canonical.com>
@roosterfish did you work on that feature? What do you think? |
It should be the default behavior to move the instance to another node if the same cluster group (containing multiple members) is given. There are two checks for this in the # c1 can be moved within the same cluster group if it has multiple members
LXD_DIR="${LXD_ONE_DIR}" lxc move c1 --target=@default # -> move from node1 to either 2 or 3
LXD_DIR="${LXD_ONE_DIR}" lxc move c1 --target=@default # -> move from 2 to 1/3 or 3 to 1/2
# c1 cannot be moved within the same cluster group if it has a single member
LXD_DIR="${LXD_ONE_DIR}" lxc move c1 --target=@foobar3
LXD_DIR="${LXD_ONE_DIR}" lxc info c1 | grep -q "Location: node3"
! LXD_DIR="${LXD_ONE_DIR}" lxc move c1 --target=@foobar3 || false # -> fails since len(foobar3) == 1 @simondeziel was the pipeline job failing unintentionally? |
The failure was not expected however it happened like this:
So with the explanation you provided, it should have picked a non-self node as the move target. But it didn't. |
I'll look into it and try to reproduce it. |
No description provided.