Software Upgrade Process #93
Unanswered
trusch
asked this question in
Chain Builders (Cosmos SDK)
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The old way of doing a software upgrade is marked as deprecated. It was submitting a gov proposal with a SoftwareUpgrade message inside. Now the new way of doing things is to just submit the MsgSoftwareUpgrade directly and it will get intercepted by the gov router and the gov module should automatically convert it to a proposal.
Anyway, I can't submit the MsgSoftwareUpgrade, because when simulating the call in order to get an estimate for the gas, I get a strange error saying "not supported for module accounts: invalid pubkey". So somehow in the pipeline the chain treats the authority account, that I specified as the gov module account, as a regular user account and fails doing so.
My process is straight forward: Assemble the MsgSoftwareUpgrade with a upgrade plan and the authority address of the gov module. Then I sign this message with a regular user account and want to regularly submit it. But when I submit the simulate call for it, it fails. If I don't simulate, but just send it directly with a lot of gas attached, the message does not fail immediately but I also can't retrieve the TX from chain, I.e. it seems to not be processed.
Is there anything that sounds wrong about this? How do others do it? I'm currently on v0.50.9 of the SDK.
Thanks in advance!
Ps: I already posted this in the cosmos-sdk discussions before finding this place here as canonical place to post cosmos questions. I dont want to span, just figured this place may have more reach
Beta Was this translation helpful? Give feedback.
All reactions