Storagenode Updater version to show in dashboard

Ideas & Suggestions
1

I recently realised that my storagenode-updater service was still running version 1.12.3 even though my storagenode is on version 1.14.7. Is it possible to include the version of the updater in the dashboard?

2020-10-28T00:15:34.494Z	INFO	Downloading versions.	{"Server Address": "https://version.storj.io"}
2020-10-28T00:15:35.010Z	INFO	Version is up to date	{"Service": "storagenode"}
2020-10-28T00:15:35.010Z	INFO	Download started.	{"From": "https://github.com/storj/storj/releases/download/v1.15.3/storagenode-updater_windows_amd64.zip", "To": "C:\\WINDOWS\\TEMP\\storagenode-updater_windows_amd64.286276330.zip"}
2020-10-28T00:15:36.648Z	ERROR	Error updating service.	{"Service": "storagenode-updater", "error": "open C:\\Program Files\\Storj\\Storage Node\\storagenode-updater.1.15.3.exe: The file exists.", "errorVerbose": "open C:\\Program Files\\Storj\\Storage Node\\storagenode-updater.1.15.3.exe: The file exists.\n\tmain.downloadBinary:62\n\tmain.updateSelf:64\n\tmain.loopFunc:36\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tmain.cmdRun:116\n\tstorj.io/private/process.cleanup.func1.4:353\n\tstorj.io/private/process.cleanup.func1:371\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:55\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-10-28T00:22:55.508Z	INFO	Stop/Shutdown request received.
2020-10-28T00:22:59.893Z	INFO	Configuration loaded	{"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
2020-10-28T00:22:59.894Z	INFO	Invalid configuration file value for key	{"Key": "log.output"}
2020-10-28T00:22:59.894Z	INFO	Invalid configuration file value for key	{"Key": "log.caller"}
2020-10-28T00:22:59.922Z	INFO	Running on version	{"version": "v1.12.3"}
2020-10-28T00:22:59.922Z	INFO	Downloading versions.	{"Server Address": "https://version.storj.io"}
2020-10-28T00:23:00.451Z	INFO	Version is up to date	{"Service": "storagenode"}
2020-10-28T00:23:00.451Z	INFO	Download started.	{"From": "https://github.com/storj/storj/releases/download/v1.15.3/storagenode-updater_windows_amd64.zip", "To": "C:\\WINDOWS\\TEMP\\storagenode-updater_windows_amd64.016186279.zip"}
2020-10-28T00:23:03.102Z	ERROR	Error updating service.	{"Service": "storagenode-updater", "error": "open C:\\Program Files\\Storj\\Storage Node\\storagenode-updater.1.15.3.exe: The file exists.", "errorVerbose": "open C:\\Program Files\\Storj\\Storage Node\\storagenode-updater.1.15.3.exe: The file exists.\n\tmain.downloadBinary:62\n\tmain.updateSelf:64\n\tmain.loopFunc:36\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tmain.cmdRun:116\n\tstorj.io/private/process.cleanup.func1.4:353\n\tstorj.io/private/process.cleanup.func1:371\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:55\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-10-28T00:27:00.086Z	INFO	Stop/Shutdown request received.
2020-10-28T00:28:17.286Z	INFO	Configuration loaded	{"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
2020-10-28T00:28:17.297Z	INFO	Running on version	{"version": "v1.15.3"}
2020-10-28T00:28:17.297Z	INFO	Downloading versions.	{"Server Address": "https://version.storj.io"}
2020-10-28T00:28:17.793Z	INFO	Version is up to date	{"Service": "storagenode"}
2020-10-28T00:28:17.793Z	INFO	Version is up to date	{"Service": "storagenode-updater"}
2

Hy!

This is probably a feature request or ā€œideaā€, but I had problems lately with versions, and as it is discussed in the please update thread I really donā€™t want to use an automated way to update versions. (Watchtower is generally an antipattern alongside with using ā€˜latestā€™ images.)

All I want is a green/yellow/red textcolor to the version number on the dashboard (latest, ok but have new version/old version).

As I watched the source this should not be a big deal, we alreay query the version json to parse out the minimum version, we just need to add it to the data json. (Iā€™m not a go programmer, but this should be a relatively easy PR both at server and client side.)

Side notes;

  • The FAQ docs page referse to a tag page which is a dead or a private page.
  • the docker images should be tagged with versions too (like v1.28.2)
  • the ā€˜latestā€™ docker image was tagged 2 days ago but the github release was 8 days ago, this seems off and strange
  • also why new users canā€™t put more than 2 links to the posts? it would be much easier if I could link more sources
2 Likes