Release preparation v1.117

Product Discussions STORJLINGS
1

New release candidate is already deployed on QA Satellite

Changelog

General

  • 3b8e700 go.mod,go.sum: Bump oidc package version
  • fe74211 shared/dbutil/spannerutil: additional check for running tests against real Spanner
  • 5b4b8e7 shared/dbutil/spannerutil: auto create db & instance (cloud)
  • 0f8b67c shared/dbutil/spannerutil: allow defining create instance arguments
  • 0f4cd02 private/mud: helper to register interface + (optional) implementation
  • 1d4fa5e shared/dbutil/spannerutil: allow more time for dropping database
  • 7337db3 versioncontrol: reduce errors in CI log
  • 2291676 versioncontrol: flags require default or releaseDefault to be set
  • 8a81b0f scripts/release.sh: add back better ldflags
  • 7b72dad go.mod: bump storj.io/common dependency
  • cb148eb release v1.117.1-rc

Multinode

  • 6d97555 web/multinode Fix fetching trusted satellites (#7204)
  • ebb2517 web/multinode: Configure webpack code splitting (#7206)

Satellite

  • 4168734 satellite/console/consoleweb/consoleapi: implement workaround for GetProjectDailyUsageByDateRange
  • b900a68 web/satellite: make live transactions tracking async
  • 2eed51a web/satellite: ensure sso url is valid
  • 9d119dc satellite/metainfo: no rate limit error for upload req other than begin object
  • 8b03735 satellite/admin/back-office: Reduce GetUser test time
  • 7e31ba4 satellite/metainfo: congestion-based success tracker
  • 37c2624 web/satellite: add Next button to onboarding upgrade with tokens flow
  • 8c35b7f web/satellite: merge upgrade with card or token steps for onboarding flow
  • b3863b7 satellite/{console,web}: group sso routes
  • 9fae6ca satellite/repair/repairer: disable flaky TestSegmentRepairPlacementRestrictions/Spanner
  • e643104 satellite/repair/repairer: fix TestSegmentRepairPlacementRestrictions
  • bb114f3 web/satellite: improve object lock time behavior
  • 8d8d081 satellite/metabase: optimize CollectBucketTallies for Spanner
  • 07622b4 satellite/metabase: optimize DeleteInactiveObjectsAndSegments
  • a4c9f1a satellite/{console,db}: repopulate signup data on inactive user
  • db189f2 satellite/db: do not trial expire inactive users
  • 2f8bf54 web/satellite: prevent page reload on Enter click during create bucket flow
  • 7cbb7a5 web/satellite: sort project table by download and storage
  • be0d3c9 web/satellite/src/views: fix Folder Input field
  • 242a925 satellite/{web/console}: allow sso users to reset password
  • 0bac701 satellite/satellitedb: optimize unnest queries
  • 2da3b86 satellite/overlay: remove unused GetNodesNetwork
  • 405c30d satellite/analytics: track encryption method in ‘project created’ analytics event
  • 06c06a3 web/satellite: disable ‘add card’ button until after Stripe form loads
  • cd8978d web/satellite: disable lock button if retention mode is not selected
  • e352a1a satellite/metainfo: fix TestEndpoint_(Move|Copy)ObjectWithRetention
  • 121b175 satellite/metabase: add missing monkits
  • bd43f1b satellite/{console,web}: start supporting of Put/GetObjectLockConfiguration permissions
  • b80331b web/satellite: extend create bucket flow to support PutObjectLockConfiguration
  • 2d2cb6d web/satellite: add new dialog to set bucket object lock config
  • 32ee720 satellite/satellitedb: optimize Spanner GetNodes query
  • 86574eb web/satellite: set object content type
  • 7433dce web/satellite: add payment method tabs to upgrade dialog
  • 4e34b7a satellite/repair/repairer: extend restored_from_trash event

Storagenode

  • 7def353 storagenode/pieces: trashrunner is trust store independent
  • 1daa902 storagenode/mud: report version with monkit
  • 18b684a storagenode/mud: initialize piece expiration database
  • ace7f38 storagenode/mud: register blobstore.Blobs as an interface with implementation
  • fed5f7f storagenode/piecestore: reduce dependency of endpoint
  • 5817bc1 storagenode/retain: helper to run retain proces as a one-off command
  • 41cae8e storagenode/run: new lightweight main entrypoint for modular storagenode

Test

  • 2a39128 testsuite/playwright-ui: bump playwright-ui to v1.48.2
5 Likes
2

The 118 update is huge on changes for storagenodes. Embrace yourselfs! :grimacing:

3

Is it? I see this:

  • c1d668a storagenode/hashstore: hash table based store for pieces

Hopfully migration will work flawlessly.

3 Likes
5

1 Like
6

He is absolutely right.

3 Likes
7

Everyone’s obligation should be to spin up at least one new node running that new backend, to test it out properly and to compare the performance between the old and new on the same hardware.
Also, make it mandatory and the ones that will not comply will receive an unenviable forum title.

2 Likes
8

I am running my nodes in docker containers. They update automatically to newer node versions. Is it possible to switch off the auto update in order to control which node (the smallest one) is first upgraded to 118? I am also a bit worried about the migration :slight_smile:

9

I don’t think there is an official off switch, but maybe if you modify some parameters in config, you can achieve that; like version check url or check interval. They are at the bottom in config.yaml.

1 Like
10

Don’t panic. There is no migration. The old backend is still in place and active.

And even if you manage to find out how to enable it you shouldn’t. This is pre alpha state and I wouldn’t even call it experimental. The idea is that we try this on our nodes first.

8 Likes