We made a mistake with versioncontrol. It only affects users that don’t use the storagenode-updater. If you are using the storagenode-updater or the docker image you should be safe.
Here is what happened:
Up until a few days ago storage nodes have been allowed to run older versions. At some point, an outdated storage node will not get selected for uploads but otherwise still respond to download requests. The satellite will send an email warning. A few versions later the storage node binary might refuse to start. We have this in place to make sure possible error messages on the customer side are not caused by outdated storage node versions. We want to keep the storage node version in a reasonable range and shutdown the nodes that are too old.
Yesterday we deployed a change that now kills outdated storage nodes way too early. We are working on a fix but in the meantime we also want to keep these nodes in the network.
Workaround:
As a workaround we decreased the version in versioncontrol. That should hopefully allow older nodes to come back online while we are working on a fix.
Possible side effects:
We didn’t downgrade the minimum version enough to match the old behavior. If you are running some kind of self-build updater please double-check your storage node version. Also be aware that versioncontrol doesn’t return the recommended version for the moment. It does point to an older storage node version for the moment.
