Skip to content
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

Closed
4 tasks
doggystylez opened this issue Jun 20, 2022 · 7 comments
Closed
4 tasks

Comments

@doggystylez
Copy link

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

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@alexanderbez
Copy link
Contributor

@julienrbrt could you verify this by any chance please? Thanks!

@julienrbrt
Copy link
Member

I have a few other things to finish before, @likhita-809 can already have a look 🙏

@likhita-809
Copy link
Contributor

@alexanderbez this issue is getting resolved when we change the flag name to some other name instead of moniker, is this the right way to fix ?

@julienrbrt julienrbrt moved this from 📝 Todo to 💪 In Progress in Cosmos-SDK Jun 21, 2022
@likhita-809
Copy link
Contributor

@alexanderbez we already have a fix for this here: #10684
But I think we can't backport it since it is CLI breaking,

@alexanderbez
Copy link
Contributor

@alexanderbez we already have a fix for this here: #10684 But I think we can't backport it since it is CLI breaking,

@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

@likhita-809
Copy link
Contributor

@alexanderbez we already have a fix for this here: #10684 But I think we can't backport it since it is CLI breaking,

@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 +1

Let's backport and close this issue

do you want to backport this @alexanderbez ?

@likhita-809 likhita-809 added backport/0.45.x backport/0.46.x PR scheduled for inclusion in the v0.46's next stable release and removed backport/0.45.x backport/0.46.x PR scheduled for inclusion in the v0.46's next stable release labels Jun 21, 2022
@likhita-809
Copy link
Contributor

resolved in #12317

Repository owner moved this from 💪 In Progress to 👏 Done in Cosmos-SDK Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

4 participants