You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
End-rey opened this issue
Dec 16, 2024
· 0 comments
Labels
bugSomething isn't workingconfigConfiguration format update or breaking changeI4No visible changesneofs-irInner Ring node application issuesS4RoutineU3Regular
These errors appear when running several IR nodes after the application started message.
error governance/process_update.go:82 can't update inner ring list with new alphabet keys {"error": "test invocation failed: unsupported parameter noderoles.Role"}
error governance/process_update.go:91 can't update list of notary nodes in FS chain {"error": "test invocation failed: unsupported parameter noderoles.Role"}
error governance/process_update.go:100 can't update list of alphabet nodes in neofs contract {"error": "could not invoke alphabetUpdate: chain/client: contract execution finished with state FAULT; exception: at instruction 3666 (THROW): unhandled exception: \"this method must be invoked by alphabet\""}
error governance/process_update.go:100 can't update list of alphabet nodes in neofs contract {"error": "could not invoke alphabetUpdate: chain/client: contract execution finished with state FAULT; exception: at instruction 312 (SYSCALL): System.Contract.Call failed: called contract 6a715fe77786ad16a5f543e45c7ba242f196d01b not found: key not found"}
The reason is most likely that unused keys are prescribed in the main chain protocol.privnet.yml:
bugSomething isn't workingconfigConfiguration format update or breaking changeI4No visible changesneofs-irInner Ring node application issuesS4RoutineU3Regular
These errors appear when running several IR nodes after the
application started
message.The reason is most likely that unused keys are prescribed in the main chain
protocol.privnet.yml
:Steps to Reproduce (for bugs)
protocol.privnet.yml
Context
nspcc-dev/neofs-dev-env#327 (comment)
Your Environment
The text was updated successfully, but these errors were encountered: