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.

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

Status endpoint fails if there are no blocks #3481

Closed
kostko opened this issue Nov 4, 2020 · 0 comments · Fixed by #3503
Closed

Status endpoint fails if there are no blocks #3481

kostko opened this issue Nov 4, 2020 · 0 comments · Fixed by #3503
Assignees
Labels
c:bug Category: bug c:client Category: client interface c:consensus/cometbft Category: CometBFT

Comments

@kostko
Copy link
Member

kostko commented Nov 4, 2020

Currently the status endpoint (GetStatus) will fail if the node doesn't yet have any blocks because it tries to load the validator set and fails with:

{“caller”:“grpc.go:202”,“err”:“failed to get consensus status: failed to load validator set: could not find validator set for height #1”,“level”:“error”,“method”:“/oasis-core.NodeController/GetStatus”,“module”:“grpc/internal”,“msg”:“request failed”,“req_seq”:117,“ts”:“2020-11-04T13:52:24.340094029Z”}

This may be related to starting with a height greater than 1.

@kostko kostko added c:client Category: client interface c:consensus/cometbft Category: CometBFT c:bug Category: bug labels Nov 4, 2020
@kostko kostko self-assigned this Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:bug Category: bug c:client Category: client interface c:consensus/cometbft Category: CometBFT
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant