-
Notifications
You must be signed in to change notification settings - Fork 50
Closed
Labels
I4No visible changesNo visible changesS4RoutineRoutineU1Critically important to resolve quicklyCritically important to resolve quicklybugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issues
Milestone
Description
Expected Behavior
🟢
Current Behavior
2025-07-30T07:43:02.941Z error meta/notifications.go:140 can't get container data {"service": "meta data", "notification container": "616c11fbe324d23e77886ca062bc57633217082373ee0cd9ba984aeae4daafc6", "error": "read E36vNnxN7Bs16HPMf5EBWTk29aSVrDDg2Cx64nYYgbdR container: status: code = 3072 message = container not found"}
2025-07-30T07:43:02.941Z debug neofs-node/morph.go:89 new block {"index": 115}
2025-07-30T07:43:02.941Z info neofs-node/container.go:68 caught container creation, updating cache... {"id": "E36vNnxN7Bs16HPMf5EBWTk29aSVrDDg2Cx64nYYgbdR", "owner": "NTkZ2RKsckjR6XjBxHEtX6JVX7K76JZ3Wu"}
2025-07-30T07:43:02.941Z info neofs-node/container.go:71 successfully updated cache for the created container {"id": "E36vNnxN7Bs16HPMf5EBWTk29aSVrDDg2Cx64nYYgbdR"}
Possible Solution
Fix the damn thing.
Steps to Reproduce (for bugs)
Happens in tests occasionally.
Context
Regression
Doesn't look like.
Your Environment
- Version used: master 0.48.0+
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS4RoutineRoutineU1Critically important to resolve quicklyCritically important to resolve quicklybugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issues