-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
edit-validator defaults moniker to moniker in config.toml, not [do-not-modify] #12311
Comments
@julienrbrt could you verify this by any chance please? Thanks! |
I have a few other things to finish before, @likhita-809 can already have a look 🙏 |
@alexanderbez this issue is getting resolved when we change the flag name to some other name instead of |
@alexanderbez we already have a fix for this here: #10684 |
@likhita-809 I actually think it's OK to backport to v0.45 and v0.46 -- It's a bug fix and that's OK 👍 Let's backport and close this issue |
do you want to backport this @alexanderbez ? |
resolved in #12317 |
Summary of Bug
Seems to have been reported in #2423
Changing the validator info with tx edit-validator without providing moniker flag defaults it to the moniker set in config.toml, not [do-not-modify] as noted in the CLI
Version
server_name: gaiad
version: v7.0.2
cosmos_sdk_version: v0.45.4
tendermint: v0.34.19
Steps to Reproduce
Start local test chain with gaiad v7.0.2, setting validator moniker in gentx to "test-0".
Query validators and note that the moniker is "test-0"
Stop gaiad and edit moniker in config.toml to "test-1"
Restart gaiad and submit a edit-validator transaction, such as
gaiad tx staking edit-validator --details "test"
. Moniker flag is omitted.Query validators and now moniker is "test-1"
For Admin Use
The text was updated successfully, but these errors were encountered: