-
Notifications
You must be signed in to change notification settings - Fork 929
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
Storage: Recover BTRFS pools source
to block device UUID to align with creation process
#13184
Conversation
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.
Cool!
Er not sure whats going on with dqlite:
|
Yeah I already restarted the jobs, same result. I have checked https://github.com/canonical/dqlite/ and https://github.com/canonical/go-dqlite/ but the last changes are from weeks/months ago. |
…mes out Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
When creating a new storage pool ensure that the config mangling is performed beforehand in FillConfig. This allows other procedures like the recovery to perform config validation without needing to actually create the pool. Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
7a5ef1e
to
6aaafed
Compare
lxd recover
for Btrfs backed poolssource
to block device UUID to align with creation process
Updated PR title to better reflect the change. |
Fixes #12605.
This moves the replacement of the pools
source
property from path to its block UUID intoFillConfig()
. The recovery procedure can now reconstruct all of the pools config without actually creating the pool using the drivers function.Additionally this addresses an unhandled timeout in 79c1780.