Closed ingoke closed 1 year ago
@N-o-Z the fix https://github.com/treeverse/lakeFS/pull/6039 probably will probably fix one too
@nopcoder Thanks, @ingoke This is fixed in v0.103.0 Please let us know if you succeeded in migrating
Thank you so much for fixing this issue ad hoc. I really appreciate the immediate response.
What happened?
Current Behavior: After trying to upgrade from v.0.90.1 to v0.102.2, I have executed lakefs migrate up (with the new version).
As a results I've got Migration failed: wrong starting version 1: wrong kv version
Expected Behavior
Expected Behavior: I'd expect that migrate up runs successfully.
lakeFS Version
v0.102.2
Deplyoment
on-premise with minio
Affected Clients
lakectl
Relevant logs output
Contact Details
ingo.kemmerzell@gi-de.com