Changelog v1.50.4

Product Discussions STORJLINGS
1

The changelog can be found here: Release v1.50.4 · storj/storj · GitHub

For docker nodes
Usually, we ask docker node operators to not update to a new version too early because of the risks. This time we need as many nodes as possible updating early to 5f2777af9-v1.50.4-go1.17.5 The reason for this is that the new docker image contains the Linux updater. We haven’t been able to test it on all operating systems and architectures. So this is the last chance to find and fix potential bugs in time before the docker image gets pushed to all docker nodes.

2

I updated the node to version 5f2777af9-v1.50.4-go1.17.5. But the web interface displays v1.49.5. Is that right? Or am I doing something wrong?

Capture
Capture1054×38 2.8 KB

Capture2
Capture2785×237 14.8 KB

3

That is correct. The new docker image should follow the rollout cursor. At the moment the rollout cursor is telling 10% of all nodes to update. The remaining 90% will stay at v1.49.5. The next rollout step would be 25%.

4

I have updated a working node. For me too the dashboard says 1.49.5

1
1900×210 14.4 KB

In Container Station

2
21078×49 7.71 KB

5

If I have multiple nodes, will they get updated at the same time? What identifier is the cursor using to identify when to update?

6

I have manually updated a node.
The dashboard now shows the correct version

1

7

Wouldn’t it be better to use an image like :beta or something that can be held up to date. Otherwise nodes may get stuck on an old image that will node be updated whenever the next update happens. (I realize that might be a while as the intention is to not update the container anymore, but you never know)

7 Likes
8

The NodeID is used to compare with the cursor.
So your nodes will not be updated in the same time.

1 Like
9

In production already?
What if my node crashes then?
Will it be broken forever?

Indeed.

1 Like
10

No, if it doesn’t work, report back and revert to the latest image. The node version hasn’t actually changed yet, so it’s not even a downgrade. Just a different way of getting the node software.

11

We better find out now while you are sitting in front of your machine. Later this week it will get pushed to all nodes anyway.

12

didn’t work for me, raspberry pi 4 arm7

downloading storagenode-updater
--2106-02-07 06:28:16--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=arm
Resolving version.storj.io (version.storj.io)... failed: Try again.
wget: unable to resolve host address 'version.storj.io'
Aborted (core dumped)
http://: Invalid host name.
13

Please provide information

uname -a
14

Linux serverpi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux

1 Like
15

This suggest that the DNS is not working, as it should. Could you please add to your docker run command the option --dns 8.8.8.8 before the --name storagenode option?

16 
docker pull storagenode:5f2777af9-v1.50.4-go1.17.5

Right?

17

something changed after adding the --dns option, but still failing. I noticed a weird date/time

downloading storagenode-updater
--2106-02-07 06:28:16--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=arm
Resolving version.storj.io (version.storj.io)... 35.224.88.204
Connecting to version.storj.io (version.storj.io)|35.224.88.204|:443... connected.
Unable to establish SSL connection.
http://: Invalid host name.
downloading storagenode-updater
--2106-02-07 06:28:16--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=arm
Resolving version.storj.io (version.storj.io)... failed: Try again.
wget: unable to resolve host address 'version.storj.io'
Aborted (core dumped)
http://: Invalid host name.
18

This assuming the cursor doesn’t jump from 10% to 25%, but slowly goes one by one?

19

Do I need to turn of watchtower when I update to test this image ?

20

I don’t know, I didn’t do that