We now have a Linux storage node and updater available. The Linux installer and the new docker container are not yet available. That means for now we have to create the required services manually. If you don’t know how that works please skip this test round and come back later when we have the installer or the docker container ready. Please don’t migrate any existing storage node. Better start a fresh storage node and expect it to get disqualified. If you are still willing to help us testing the Linux installer here is the plan:
Download the storagenode and storagenode-updater v1.15.3. Soon the v1.16.1 rollout will start and this gives us the opportunity to test if the updater is behaving as expected.
Both way would work. You can run them manually first or you create the services first. I would say it depends on how confident your are. How many restarts do you expect to get your storage node up and running? If the answer is “I have no idea” then better start with manual execution.
We simply wait a few days until it is time for your node. The v1.16.1 rollout has started today and I will keep you updated every time the rollout cursor increases.
I could setup a version server that would allow us to play this game within minutes.
I would prefer option 1 because that way we might discover some additional bugs that option 2 would not find. We could run both tests by setting up a second test node. Is it worth it? I think we can still do that if we notice that something is not behaving as expected.
systemctl status storagenode-updater would allow you to see the last log lines without having to enable additional logging. That is what I am using currently.
