qanet ec2 nodes forked

[rsporny]

Context & versions

• node-1.0.0-rc.5
• qanet ec2 nodes forked

Steps to reproduce

1. see telemetry

Expected behavior

nodes not forking

Actual behavior

node forking

[rsporny]

we need to:

1. understand why devnet is down again - that's impacting qanet ec2 nodes: @erik-axeljakobsson
2. understand why qanet ec2 nodes forked again - @gilescope
3. wipe qanet ec2 nodes and let the sync as a quick win @erik-axeljakobsson

[scottbuckel]

We spent a little bit of time debugging, this is what I believe happened:

Looks like this was an issue related to the fork testing - we updated dbsync version and it took longer than block_stability_margin. The ec2 nodes got banned. we tried restarting them, but that's not what we have to do with a ban - we have to restart the peers that are doing the banning.

The nodes were actually wiped and started syncing. They should be sync'd up in a few hours.