From 26849ed0665cc49a99c98ed084971a7db7201bae Mon Sep 17 00:00:00 2001 From: Alex Auvolat Date: Thu, 27 Jan 2022 14:31:25 +0100 Subject: [PATCH] Add step to 0.6.0 migration guide --- doc/book/src/working_documents/migration_06.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/book/src/working_documents/migration_06.md b/doc/book/src/working_documents/migration_06.md index 4312e37d..687f7458 100644 --- a/doc/book/src/working_documents/migration_06.md +++ b/doc/book/src/working_documents/migration_06.md @@ -38,9 +38,13 @@ The migration steps are as follows: the buckets that existed previously. This will also give access to API keys as it was before. -9. Check that all your buckets indeed appear in `garage bucket list`, and that - keys have the proper access flags set. If that is not the case, revert - everything and file a bug! +9. Do `garage repair -a --yes tables` and `garage repair -a --yes blocks`, + check the logs and check that all data seems to be synced correctly between + nodes. -10. Your upgraded cluster should be in a working state. Re-enable API and Web +10. Check that all your buckets indeed appear in `garage bucket list`, and that + keys have the proper access flags set. If that is not the case, revert + everything and file a bug! + +11. Your upgraded cluster should be in a working state. Re-enable API and Web access and check that everything went well.