mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Complex object sometimes can't be fetched from certain nodes when bearer token is attached #875
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#875
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @alexvanin on GitHub (Nov 10, 2022).
Originally assigned to: @carpawell on GitHub.
I am trying to upload and download object with bearer token. I use wallets from neofs-dev-env:
wallets/wallet.jsonas container owner,services/s3_gate/wallet.jsonas request sender.Expected Behavior
All storage nodes in the system return complex object.
Current Behavior
Some container nodes return
object not founderror.When bearer token is not attached, object is fetched (from public container).
Steps to Reproduce (for bugs)
I used
REP 2 IN X CBF 1 SELECT 3 FROM * AS Xso I had:services/s3_gate/wallet.jsonis attached to this issue.Context
GET requests are failed on container nodes which contain some split information.
These nodes try to send inter-container requests to fetch the one of the child objects from container nodes, but they fail.
See more logs in attachment below.
Node sends new requests to container nodes and attaches bearer token from original request. Bearer token integrity check fails there.
nspcc-dev/neofs-node@d8d3588e1b/pkg/services/object/acl/acl.go (L252-L255)Possible Solution
Do not attach bearer token for inter-container communication. It should work fine considering that only container nodes are assembling the objects right now (see https://github.com/nspcc-dev/neofs-node/issues/838)
Your Environment
b.json
s03-get-logs.txt
@carpawell commented on GitHub (Nov 10, 2022):
@fyrchik, @acid-ant, @cthulhu-rider, depending on the "speed of the fix", solution for #838, and some other preferences i see two main possibilities:
@fyrchik commented on GitHub (Nov 12, 2022):
Closed via #2045