mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
It looks like removed object can be searched after removal #1410
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#1410
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 @smallhive on GitHub (Apr 25, 2025).
Originally assigned to: @cthulhu-rider on GitHub.
There is s3 gate test, which sometimes fails.
The fail rate is about 1:350, which is very difficult to detect and debug.
Eventually got the next S3 Gate log
Expected Behavior
Object
b2LpEDyeSsqCDfnAvTEmakfNTiX7WYfK6WbRfTCg3cjremovedCurrent Behavior
Object
b2LpEDyeSsqCDfnAvTEmakfNTiX7WYfK6WbRfTCg3cjfound via search v2Steps to Reproduce (for bugs)
Run test a lot of times
Regression
No, I don't think so
@roman-khimov commented on GitHub (Apr 28, 2025):
It looks like the node doesn't do the request properly or not interpreting 2052 correctly. It's tombstone verificator that is doing this request and freaking out on 2052, not even the gate itself. Same things happens to report uploader from time to time:
https://github.com/nspcc-dev/neofs-rest-gw/actions/runs/14710063058/job/41279915286
@cthulhu-rider commented on GitHub (Apr 29, 2025):
@smallhive may u pls try fix #3332?
@smallhive commented on GitHub (Apr 29, 2025):
Sure
@smallhive commented on GitHub (Apr 29, 2025):
I ran the test 1500 times - everything is green. Previously, it was about 5 failures for such attempts.
It looks like the issue is gone. @cthulhu-rider