-
Notifications
You must be signed in to change notification settings - Fork 50
Open
Labels
I4No visible changesNo visible changesS4RoutineRoutineU3RegularRegularbugSomething isn't workingSomething isn't workingconfigConfiguration format update or breaking changeConfiguration format update or breaking changeneofs-irInner Ring node application issuesInner Ring node application issues
Description
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:
ProtocolConfiguration:
Genesis:
Roles:
NeoFSAlphabet:
# 4 ir
- 0345eefc50545e83dfc7ec9ab648210dddbeb3996912a8ff6416e2d3ec51a8e324
- 039a1c33ed18bb57f6e6b3e712b54b924d2b9137c4906cf433ee8693a3810e380e
- 02d3088931c034a390c5bea16d19ef2debe9702019270c94913528a8ac30e17373
- 02fb7531661401222dcf2711bbd78597e8152ba886612e44ea530a08bbe4eba810
# 7 ir
- 022c0bf9e1a0c864905d2b8909555ae421db9a52f86ab268a84d9be42a6ad9d858
- 024a640c8cbe3e34f0cd927950c64f6d0d239770397fe645d52bf920fddd655bf8
- 024f19ec7a8e35722c8cdd7d21fcc2090f2658b2fd67b7b23f1936dc5e7b54b216
- 03797de54a6abb6d19c22a5afabf30d320a9348b0f294315e74cb3b423b1ac9dc9
- 03a90f6e7dcb49cf9603dde786781c4fdbd43f8a57c5b23fe93d4ecc33952599fd
- 03c7aa35ab64aad9b85a35647b1f0aec59344271a6c2ed7644faf1997ee098bbab
- 02ca9097295d28e28e2ae55eb62ca0b1ac48b2d9b6dcb64ddb936a64d80cb8b795
Steps to Reproduce (for bugs)
- Use unused keys in the main chain
protocol.privnet.yml - Start several IR nodes configuration
Context
nspcc-dev/neofs-dev-env#327 (comment)
Your Environment
- Version used: IR_VERSION=0.44.1, NEOGO_VERSION=0.107.1
- Server setup and configuration: DevEnv (9cdbda6)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS4RoutineRoutineU3RegularRegularbugSomething isn't workingSomething isn't workingconfigConfiguration format update or breaking changeConfiguration format update or breaking changeneofs-irInner Ring node application issuesInner Ring node application issues