-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test IR change with main chain role change #943
Comments
@roman-khimov questions:
|
|
@roman-khimov need to clarify a change scenario a little bit, cause I'm keep getting We need to deploy main chain + 4 IR nodes. And what should be the next step? Cause I tried to shrink the list of alphabet nodes specified here:
But seems like it is not allowed. Then I tried to specify 3 nodes in the list above, but Also can you point me to the right command to check the list of designated roles? both from main chain and fs chain. For the main chain I tried to use:
But it doesn't return a list of pubkeys. |
Part of #943 Signed-off-by: Evgeniy Zayats <[email protected]>
Part of #943 Signed-off-by: Evgeniy Zayats <[email protected]>
Part of #943 Signed-off-by: Evgeniy Zayats <[email protected]>
Part of #943 Signed-off-by: Evgeniy Zayats <[email protected]>
How many keys have you put into the role? If you have 4 CNs and 4 IRs there should be 4 keys set, easy as that.
That's genesis, you can't change it on a running network.
Exactly as expected, that can be one of the test steps, you set the same key set --- nothing changes. We need to change the list. Run a CN/IR node with a different key, set it into config, check that the list of validators has changed and it works (and the old node can be removed).
Keys are base64-encoded here (refs. nspcc-dev/neo-go#3602). |
@roman-khimov Started 4 IRs + single main chain node. Started additional IR node with the following config: ir_node_config_bejrlmqaiq.txt
Got the following in existing IRs:
Full IR log after receiving the update:
Is it another misconfiguration from my side? |
Is your feature request related to a problem? Please describe.
I'm always frustrated when we don't have tests for some core NeoFS things.
Describe the solution you'd like
Test IR change in 4-node IR scenario with main chain. IR is controlled by the designation contract on main chain, it's the same as IR set initially, but main chain committee can set it to any other list of nodes and FS chain must follow this change. IR includes CNs, both change in this setting.
Additional context
neo-project/neo#2267
The text was updated successfully, but these errors were encountered: