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

Add mainnet node canary that fails when syncing to tip fails/panics #1286

Closed
Tracked by #745
dconnolly opened this issue Nov 12, 2020 · 0 comments · Fixed by #1461
Closed
Tracked by #745

Add mainnet node canary that fails when syncing to tip fails/panics #1286

dconnolly opened this issue Nov 12, 2020 · 0 comments · Fixed by #1461
Assignees
Labels
A-infrastructure Area: Infrastructure changes

Comments

@dconnolly
Copy link
Contributor

We want to do a full sync to tip (with checkpoint sync on) that only fails and alerts/displays the failure if something bad happens when syncing to tip.

We might be able to do this at the gcloud instance group healthcheck level by grepping logs or something, but worse comes to worse we can use GH Actions to deploy a zebrad container node and just watch it run via an open ssh session and if it fails it fails the job/step, lol.

@dconnolly dconnolly added the A-infrastructure Area: Infrastructure changes label Nov 12, 2020
@dconnolly dconnolly added this to the First Alpha Release milestone Nov 12, 2020
@dconnolly dconnolly self-assigned this Nov 12, 2020
@dconnolly dconnolly mentioned this issue Dec 4, 2020
@dconnolly dconnolly linked a pull request Dec 4, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-infrastructure Area: Infrastructure changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants