micropelago/garage
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add step to 0.6.0 migration guide

Browse Source
This commit is contained in:
Alex Auvolat 2022-01-27 14:31:25 +01:00
parent c99f55c420
commit 26849ed066
No known key found for this signature in database
GPG Key ID: EDABF9711E244EB1
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/book/src/working_documents/migration_06.md
View File

@ -38,9 +38,13 @@ The migration steps are as follows:
the buckets that existed previously. This will also give access to API keys the buckets that existed previously. This will also give access to API keys
as it was before. as it was before.
9. Check that all your buckets indeed appear in `garage bucket list`, and that 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. 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 keys have the proper access flags set. If that is not the case, revert
everything and file a bug! everything and file a bug!
10. Your upgraded cluster should be in a working state. Re-enable API and Web 11. Your upgraded cluster should be in a working state. Re-enable API and Web
access and check that everything went well. access and check that everything went well.