Release preparation v1.143

New release candidate v1.143 is already deployed on QA Satellite
List of changes:

Changelog

Satellite

  • 356ff80 satellite/metabase/changestream: avoid fmt.Sprintf in SQL
  • 885e52c web/satellite: update css
  • 2a499ec satellite/metabase/changestream: increase max timeout for test cleanup
  • 93c200c satellite/metabase/changestream: log errors in processor
  • ffe45bd satellite/payments: add logging when ProcessRecord fails
  • fe89fd4 satellite/satellitedb: create new bucket_migrations table
  • eb86b4a satellite/admin-ui: fix user/project state update bug
  • bc7fcc5 satellite/console/consoleweb: add compute gateway URL to CSP
  • 218f5d1 satellite/valdi: make the valdi client optional for modular console
  • 7d2c971 satellite/mailservice: wrap template parsing error
  • c5df8af satellite/metabase: fix negative version handling in Delete|Get ObjectExactVersion
  • cacf8fa satellite: added bucket migrations DB logic
  • 102ca97 web/satellite: improve remove card flow
  • fc9e942 satellite/metabase: use precommit query in delete
  • 6994c2e satellite/metabase: rename isRetentionProtected → Retention.isProtected
  • 05161dd satellite/metabase/changestream: SchedulePartitions sets scheduled_at
  • 81e32bd web/satellite: add webui to modular storagenode container
  • 0b0d5e5 satellite/metabase: avoid reading segment count from previous object version
  • 5cb3f91 satellite/satellitedb: Fix metrics reporting
  • 7c92021 satellite/console: add config for partner UI mods
  • 4711e71 satellite/metabase: simplify test object verification
  • b676c86 satellite/metabase: simplify test object verification part 2
  • 1d9b6e7 web/satellite: get partner UI config from backend
  • 1b85db8 satellite/console: add white label config
  • 981622e satellite/{console,tenancy}: create tenant context system for request-level tenant identification
  • 5717d95 satellite/payments/stripe: reduce number of queries to spanner
  • 63897d4 satellite/metabase: reuse object (if possible) when committing unversioned objects
  • 5bae544 satellite/metabase: simplify test object verification part 3
  • 8f03e82 satellite/metabase: add EncodeSpanner/DecodeSpanner for Version
  • 94c347e satellite/reputation: check node age in addition to number of audits to determine vetted status
  • 2d06d4a satellite/Dockerfile: adds the bad-passwords file directly to the image
  • 3d47568 satellite/nodeselection: unvetted selector should use threshold as a max
  • 336b8ea satellite/admin: allow abbreviated user deletion
  • 797d6e0 satellite/admin-ui: allow abbreviated user deletion
  • b137784 satellite/db: add tenant_id column to users table
  • 309e444 satellite/{console,db}: add tenantID aware db methods
  • 136c71f satellite/metabase: use Apply instead of BatchWrite in deleteObjectLastCommittedPlain
  • beaec41 satellite/metainfo: reduce test data size
  • 1de3ae1 satellite/metainfo: fix multipart upload detection in batch
  • f9621fd web/satellite: make UI config backward compatible

Storagenode

  • f8e4d8f web/storagenode: migrated simple components to use script setup syntax
  • d33cb90 web/storagenode: migrate notifications, content and error components to use SFC syntax
  • f061d96 web/storagenode: migrated and reworked charts to use SFC syntax
  • c2ecb27 web/storagenode: migrate another set of components to use SFC syntax
  • ce86a8d web/storagenode: migrated payout components to use SFC syntax
  • ef5f694 web/storagenode: remove Vue filters
  • 8b27012 web/storagenode: replace Vuex with Pinia
  • b085811 web/storagenode: upgrade Vue version along with other deps
  • 6e27be9 storagenode/{console,web}: replace vue cli service (webpack) with vite
  • 7849fe5 cmd/storagenode: fix node version for docker image
  • 8c49a04 web/storagenode,all: fix node Dockerfile, use official nodejs image and bump to 24.11.1
  • 4e52fd0 storagenode: Fix UsedSpace calculation of Storagenode web console
  • 8eddf1d storagenode/hashstore: windows fixes

Test

  • 35ba1fb testsuite/playwright-ui: regenerate lock file

Uplink

  • b920533 cmd/uplink: move backward compatibility tests from storj/uplink

Multinode

  • d55d648 multinode: add telemetry
  • 9916a84 multinode: display full used space

General

  • 22a8e9b shared/modular/cli: errgroup must cancel the context
  • 3b7dfe9 shared/modular/cli: use zeebo/errs for error handling
  • 6b59cfd claude/skills: add test-with-spanner skill
  • edceb83 all: fix ctx handling
  • d00fe29 Claude.md: teach it how to run unit tests with Spanner emulator
  • 502cede build: script and Claude files to do automatic review on Gerrit
  • fba7259 Jenkinsfile.{verify|public}: improve build time
  • f2c0856 scripts: tag-release.sh doesn’t create dedicated commits
2 Likes

Ah… the end of an Era. It used to be fun to figure out what series-of-calculations the UI must be making… to get numbers so wrong :wink:

5 Likes

1.142.7

1.143.2

1 Like


Grafana and storj multinode dashboard shows the same. Node is on hashstore.

An old joke in the AI community:

Do not anthropomorphize AI. They don’t like it.

:grin:

2 Likes

Allocated disk space display still broken in v1.143.3. Delete all databases did not help.

1 Like

Good morning, after updating the node to the new version v1.143.2, the space used by Storj is broken. I’ve deleted the databases to reset it, but it’s still the same. Also, since it became broken, it’s not receiving any data.

So downgrade it back, because you is not supposed to update it, until it is written in version.storj.io

It’s not receiving data, because you have too much, not because the UI is broken.

Based on what I see in the code.

Used/Free display is not reliable (working on this), overused must be true.

1 Like

According to Windows disk space, it says 1.68 TB is in use. Therefore, the node should have approximately 100 GB of space left to receive data, which is why it’s strange that it indicates it’s already full.

100 GB isn’t critical, but it’s confusing because I also can’t see the garbage collection to check what’s happening.

v1.143.4 is just released. Please test that one. There is a small fix related to the UI (I am still testing it, but you can also do).

For non-ui related problems, best to share the content of this URL:

http://localhost:14001/api/sno/ (this is an endpoint on the storagenode console)

The most important part is nodeId (what I can use to check what is the free space according to the satellite), and diskSpace (used on the UI to display free space).

The third important information is whether you use dedicated or shared (default) disk space calculation. (If you don’t understand this question, you use shared). The dedicated disk space calculator uses some reserved pool which couldn’t be used.

2 Likes

1.43.4 windows, hashstore, no dedicated disk. :+1:

it also looks that sattelite not report used space, I have something like this picture.

why there is no trash any more? also dead bytes can be also qualified as trash.

1 Like

There are too many categories (trash, reserved, reclaimable, etc.). Doesn’t fit easily on the right side. Instead I tried to add categories only to doughnut (move mouse over the two blue parts. There should be tool tips).

Trash represents the trash which couldn’t be deleted, yet.

“dead bytes” are called “reclaimable”, and counted as a separated category, as they can be deleted immediately.

2 Likes

I don’t have nodes on 1.143 yet.
Were there any changes made to the API? I hope it won’t break my setup. As I pull the data from there.

What I would like to see and have in the API without any quirks is:

  1. Space occupied and paid
  2. Space occupied and unpaid
  3. (Space up for deletion if not 2.)
  4. Allocated Space
  5. Free space

And of course the numbers should align with the CLI dashboard which was more accurate displaying the free space and the OS.

1 Like

I tested version v1.143.4, and now it appears like this on my dashboard:

I’ll send you the data I obtained from http://localhost:14002/api/sno/ privately so you can review it.

Regards

Just an idea. If you would use a stacked bar chart, the graph area would be narrower and there would be enough space on the right side for the data labels.
A percentage scale on the left with 0% on the bottom and 100% on top. 100% is equal with allocated space. If there is any overuse, the scale would go over 100%. The bar would be like Used, Trash, Reclaimable, Free, Overused from bottom to top.
The data labels would be on the right side, and I would use GB everywhere instead of TB/GB mixed.

1 Like