Evmosd status reports incorrectly catcing_up: false when node is actually syncing
Summary of Bug
In normal situation evemosd status reports
"catching_up": false when a node is fully synced with the network head.
It incorrectly reports "catching_up": false when the node is out of sync and catching up with the network head, like in the initial sync state.
It should report "catching_up": true so monitoring software can determine that node is syncing without external reference.
Version
All versions from the release
Steps to Reproduce
Under the condition of issue890 when node is out of sync for 50-1000 blocks it incorrectly reports "catching_up": false which is not true, because a node is out of sync actually and catching up with the network head. In most cases a node is able to sync up with the network finally, but during this period it may provide incorrect status.
Additional context
Node restart fixes this issue at all times, but the report may become incorrect again quite quickly, after several hundreds synced blocks under continuous load, without smart height balancer.
For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged
- [ ] Contributor assigned/self-assigned