Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Node booted up even though metabase is outdated #1860

Closed
anikeev-yadro opened this issue Oct 10, 2022 · 0 comments · Fixed by #1888
Closed

Node booted up even though metabase is outdated #1860

anikeev-yadro opened this issue Oct 10, 2022 · 0 comments · Fixed by #1888
Assignees
@carpawell
Labels
bug Something isn't working U3 Regular

Comments

@anikeev-yadro
Copy link

Related to #1809

Expected Behavior

Node should not boot up if metabase is outdated

Current Behavior

Node booted up even metabase is outdated

Steps to Reproduce (for bugs)

  1. Start neofs-node v0.32
root@az:/home/service# /home/service/neofs-node --version
NeoFS Storage node
Version: v0.32.0
GoVersion: go1.18.4

Log: start neofs-node v0.32.0.txt

  1. Then stop v0.32 and start v0.32.0-73-g01ddb3f8.
    Node started successfully
root@az:/home/service# /usr/bin/neofs-node --version
NeoFS Storage node
Version: v0.32.0-73-g01ddb3f8
GoVersion: go1.18.4

Log: start neofs-node v0.32.0-73-g01ddb3f8.txt

Your Environment

Server setup and configuration:
cloud, 4 VMs, 4 SN, 4 http qw, 4 s3 gw

Operating System and version (uname -a):
linux vedi 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
@carpawell carpawell self-assigned this Oct 12, 2022
@carpawell carpawell mentioned this issue Oct 12, 2022
Merged
@carpawell carpawell added 2022Q4 and removed 2022Q3 labels Oct 14, 2022
@alexchetaev alexchetaev added 2022Q3 and removed 2022Q4 labels Oct 14, 2022
aprasolova pushed a commit to aprasolova/neofs-node that referenced this issue Oct 19, 2022
@carpawell @aprasolova
[nspcc-dev#1860] meta: Fix 0,1 -> 2+ version migration
2306185 
In the 2nd version, there was a database format change: buckets have changed
their keys, so it becomes impossible to check the version in the 1 -> 2+
migrations because of different buckets that store info about the version.

Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carpawell carpawell

Labels
bug Something isn't working U3 Regular
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix/1 -> 2+ meta version migration
3 participants
@carpawell @alexchetaev @anikeev-yadro