Private bucket test failures #530

New issue

Closed

opened 2025-12-28 17:37:42 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:37:42 +00:00

Owner

Originally created by @roman-khimov on GitHub (Aug 6, 2025).

Originally assigned to: @smallhive on GitHub.

Current Behavior

🔴
https://rest.fs.neo.org/7ZVSQHtioVRiDT2btN9xEmQhczXV9vryCEAHUawfD8Sc/772-1754470576/index.html#suites/6d7c9ec7c4f3e4460ae14fd266a64e04/1630b471a204ebd2/

call method {"status": 500, "request_id": "46666f7b-6cd6-4186-8970-72b420eb528b", "method": "GetObject", "bucket": "yournamehere-uchzguxgslfd3oyu-144", "object": "foo", "description": "could not find object", "error": "search object version: search objects with cursor: search objects: status: code = 1024 message = bearer token owner differs from the request sender"}

Expected Behavior

🟢

Possible Solution

Likely some bearer token setup fix is needed.

Steps to Reproduce

Run tests.

Context

Seems to be related to 0.45.0->0.48.1 node upgrade (#1197). New node does more checks and some token that was always incorrect is completely rejected now.

Regression

Not likely.

Your Environment

Version of the product used: 0.40.0+
Server setup and configuration files used: 0.48.1 node

Originally created by @roman-khimov on GitHub (Aug 6, 2025). Originally assigned to: @smallhive on GitHub. ## Current Behavior 🔴 https://rest.fs.neo.org/7ZVSQHtioVRiDT2btN9xEmQhczXV9vryCEAHUawfD8Sc/772-1754470576/index.html#suites/6d7c9ec7c4f3e4460ae14fd266a64e04/1630b471a204ebd2/ > call method {"status": 500, "request_id": "46666f7b-6cd6-4186-8970-72b420eb528b", "method": "GetObject", "bucket": "yournamehere-uchzguxgslfd3oyu-144", "object": "foo", "description": "could not find object", "error": "search object version: search objects with cursor: search objects: status: code = 1024 message = bearer token owner differs from the request sender"} ## Expected Behavior 🟢 ## Possible Solution Likely some bearer token setup fix is needed. ## Steps to Reproduce Run tests. ## Context Seems to be related to 0.45.0->0.48.1 node upgrade (#1197). New node does more checks and some token that was always incorrect is completely rejected now. ## Regression Not likely. ## Your Environment * Version of the product used: 0.40.0+ * Server setup and configuration files used: 0.48.1 node