-
Notifications
You must be signed in to change notification settings - Fork 50
Closed
Labels
I4No visible changesNo visible changesS4RoutineRoutineU2Seriously plannedSeriously plannedbugSomething isn't workingSomething isn't workingneofs-cliNeoFS CLI application issuesNeoFS CLI application issuesneofs-irInner Ring node application issuesInner Ring node application issuesneofs-storageStorage node application issuesStorage node application issues
Milestone
Description
Expected Behavior
Client error when control service can't do something.
Current Behavior
./neofs-cli --config /home/runner/work/neofs-node/neofs-node/neofs-testcases/test-run-2025-12-12-12-46-22-437272/env_files/neofs-env-2025-12-12-13-35-18-140468875602816/inner_ring_btscrmukxu/ir_cli_config_mgsamroofj.yml control notary request --address 'NNzVrPZKboWnhV7VAJboPLitCxPmyuSHg4' --endpoint 'localhost:35457' --wallet '/home/runner/work/neofs-node/neofs-node/neofs-testcases/test-run-2025-12-12-12-46-22-437272/env_files/neofs-env-2025-12-12-13-35-18-140468875602816/ir_alphabet_goeflyagzl/alphabet1.json' --method 'removeNode' 03ed92cf9dde91bf35d7d806130ce7c22cbdb639dbb59e77b0fb87287359cbf88d
RETCODE: 0
STDOUT:
Transaction Hash: 0000000000000000000000000000000000000000000000000000000000000000
STDERR:
It failed because of #3737 and the error can be clearly seen in node logs, but client receives an empty hash and no error.
Possible Solution
Fix something.
Steps to Reproduce (for bugs)
Make some control service call fail internally like above, see how client reacts.
Context
Regression
Not likely.
Your Environment
- Version used: master
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS4RoutineRoutineU2Seriously plannedSeriously plannedbugSomething isn't workingSomething isn't workingneofs-cliNeoFS CLI application issuesNeoFS CLI application issuesneofs-irInner Ring node application issuesInner Ring node application issuesneofs-storageStorage node application issuesStorage node application issues