Closed roeierez closed 3 weeks ago
From what I can tell this is related to maybe_upgrade
not completing before the node gets scheduled, causing the old version to be started, which doesn't match with the signer version, which then causes the crash. I'll dig into this further
Thanks. Perhaps also worth also stopping the node right after maybe_upgrade (in case of real upgrade) because the node can be online at that time.
Yep, that's the plan. Actually stopping would already be sufficient as it'd be immediately rescheduled by the client connecting 👍
This has been merged and will be deployed on the server side tomorrow 👍
Confirmed that this is no longer an issue.
On first run when upgrading to master the node crashes. Seems like it is a result of signer upgrade.