Nodes not upgrade to new version 145.3. WHY?

[digitalfrank]

Hi to all, my 20 nodes not upgrade to new version. Why? the actual version is 142.7 but i view that the version released is 145.3.
from this site https://version.storj.io/ the version that i have it’s correct but because the new version isn’t released? What’s the problem?

[Vadim]

storj will decide when it is ready for update.

[Alexey]

When we are ready, we will start a rollout. Please, let the node alone

If you want to have adventures, you may take a look on this thread:

Please join our public test network

Let’s answer the most important question first. The test network is unpaid. You will not get any payout from the test satellite. Now you might ask why should I join the satellite if you can’t earn money? Well, you should do it for several reasons: You can make sure your specific setup works with any new version. You will be able to identify possible problems early in the test network. You are welcome to cheat our system. Do you have an idea in mind about how to cheat our audit system but it i…

[digitalfrank]

of course, my nodes are online 24/7/365 and the upgrade is automatic when the my node id is present on rollout, but I was just curious to know why it’s been so long. The old version is now over 2 months old, and storj usually updates regularly at least once a month. Thanks a lot and i stay online for ever. Storj it’s “Simply the Best” (cit. T. Turner) .

[Alexey]

Holidays, also not all features were tested fully. Why is it so important for you?

[digitalfrank]

You’re right, it shouldn’t actually be necessary unless forced by bugs or substantial improvements, but unfortunately I’m a “sucker” for updates and would like to always have everything updated to see new features and verify bug fixes. The link you sent me is actually interesting; I think I’ll activate a test node. I have so many old 3TB HDDs that I can afford to activate one. If I remember correctly, when Storj asked some node operators to sign up for an online service to test the new versions, I participated and tested the beta version when they transitioned from test data to real data. I’m waiting for the new updates as soon as you’ve completed all the tests. Thanks.

[Ambifacient]

You can manually update yourself, just replace the binary files. In docker it’s either in /app/bin/ or /app/config/bin/ depending on which container version you have.

[Alexey]

I would not recommend to use not released versions on a production network, they could be not compatible. If they also have a database migration, then you will be unable to downgrade without losing a database.
The best method to see/test new versions is to subscribe to the QA satellite using the link above.

[digitalfrank]

I never update manually, precisely because of what’s been written in previous posts. If the version I have is the official one released and tested for everyone, I leave it that way. I let Storj decide whether to roll out the updates. They certainly have the “power” to know if that version is bug-free and/or necessary for the upgrade of all global nodes. In this case, I’ll be a “stupid” employee and wait for the releases. My initial question was legitimate because I saw it hadn’t been updated in a while, and I know that nodes can’t be running versions that are two versions older than them, otherwise they’ll no longer download data from the network. I noticed that in the previous rollout, the minimum version indicated was 1.41.2, so all nodes can be running 1.42.7. Thanks everyone.

[Rinos]

I don’t understand why people are so obsessed with updates. Personally, I prefer updates that actually fix bugs, add something extra, or optimize the system.

I don’t understand…

But that’s probably why I like using Debian and hardly ever use Microsoft.

I think the team is preparing a version with lots of new features : and improvements that will be great.

But stop stressing the developers. Just because there’s no new version doesn’t mean the system isn’t improving. I imagine they’re also working on the server code and testing lots of things locally. People are becoming less and less patient…

[Roxor]

Yeah, I get that they’re still working on hashstore… but after that I’d be fine with node updates every 3-6 months. Satellite and customer/UI code can probably always benefit from upgrades… but at some point storing+providing the data should be basically “done”.

[Unique]

I’ve been upgrading manually for a couple of years now, ever since the auto update started crashing my nodes. Something about can’t find the database. And yes I did put it on the forum but nothing fixed it. I wait until it says Latest Release and install that. Have a script that I to put the version in to install and its auto from there.

[Alexey]

All nodes uses versions

@digitalfrank

from this site https://version.storj.io/

so, the diff between versions is estimated based on it too. Even if the node is not updated to the latest build, the current and recommended will be the base.