-
Notifications
You must be signed in to change notification settings - Fork 50
Description
Expected Behavior
No errors in logs.
Current Behavior
Oct 07 10:55:57 titan2 neofs-node[552576]: warn neofs-node/container.go:240 put report to contract error {"component": "containerReports", "epoch": 24604, "epoch": 24604, "epoch": 24604, "epoch": 24605, "epoch": 24605, "epoch": 24605, "epoch": 24606, "epoch": 24606, "epoch": 24606, "epoch": 24607, "epoch": 24607, "epoch": 24607, "epoch": 24608, "epoch": 24608, "epoch": 24608, "epoch": 24609, "epoch": 24609, "epoch": 24609, "epoch": 24610, "epoch": 24610, "epoch": 24610, "epoch": 24611, "epoch": 24611, "epoch": 24611, "epoch": 24612, "epoch": 24613, "cid": "E9X5uoYexPdRjGTwyrvuM2a1hFjoNdhQGJtBq4MUsmUt", "error": "could not invoke method (putReport): chain/client: contract execution finished with state FAULT; exception: at instruction 8316 (THROW): unhandled exception: "method must be invoked by storage node from container""}
Possible Solution
Looks like it stores some objects from containers it doesn't belong to now (but was belonging to previously, this assumption needs to be checked anyway). Reporting estimates makes no sense in this case.
Steps to Reproduce (for bugs)
Create a REP 1 container, add an object, add more nodes, make it so that the old node is no longer a part of container, but still stores something.
Context
Testnet.
Regression
Yes and no, previously it was hidden by complex estimation protocol. After #3460 we can see this in logs.
Your Environment
- Version used: 0.49.0
- Server setup and configuration: testnet node
- Operating System and version (
uname -a): Debian oldstable