-
Notifications
You must be signed in to change notification settings - Fork 38
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
test/includes/microcloud: Remove core.trust_password
support
#323
Conversation
e741faa
to
d5bed11
Compare
core.trust_password
support
dfdb554
to
1573d16
Compare
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
1573d16
to
151b514
Compare
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
7f6681b
to
4ce75af
Compare
4ce75af
to
a4278f7
Compare
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
a4278f7
to
dd2b538
Compare
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
Will mark as draft until I have finalized the testing on my end. |
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
That is now ready for a final review. I have tested forming LXD clusters in version 5.21 (prior to password removal) and edge. There was an error in the |
The pipeline is now failing due to a regression caused by canonical/lxd-pkg-snap#471. |
@@ -309,6 +309,14 @@ func (s *LXDService) HasExtension(ctx context.Context, target string, address st | |||
} | |||
} | |||
|
|||
// Fill the cache of API extensions. | |||
// If the client's internal `server` field isn't yet populated | |||
// a call to HasExtension will always return true for any extension. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a corresponding fix for this in LXD?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we discussed earlier I'll follow up on this in LXD.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @roosterfish
@@ -200,7 +200,7 @@ func (s LXDService) Join(ctx context.Context, joinConfig JoinConfig) error { | |||
|
|||
err = op.WaitContext(ctx) | |||
if err != nil { | |||
return fmt.Errorf("Failed to configure cluster :%w", err) | |||
return fmt.Errorf("Failed to configure cluster: %w", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to have turn up a No matching cluster join operation found
error in https://github.com/canonical/microcloud/actions/runs/9611369723/job/26518376077?pr=323#step:13:58498
That's an error I also saw pop-up from time to time in the LXD test suite. Anyway, not relevant for this PR but would be nice to have that one addressed in LXD ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it might be a race between creating the operation and checking for it.
This was fixed by canonical/lxd-pkg-snap#476 and now tests are working. |
This is required after canonical/lxd#13567. Instead of the password we now have to use a token when adding the remote.