-
Notifications
You must be signed in to change notification settings - Fork 329
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
Chain-id upgrade fails upgrading IBC client in remote chain #3057
Comments
I managed to reproduce this. Thank you @RaulBernal for submitting the issue. It's not clear what the problem is. Your reproduction steps are very thorough, so I won't cover that. I'll just paste here the detailed log on how the failure looks like:
|
The proposal generated by hermes test CLI is wrong, as in the client state doesn't reflect the chain id change. When building the hermes/crates/relayer/src/upgrade_chain.rs Lines 71 to 74 in 097c5df
we must also make sure:
|
just tested with temp fix in |
Summary of Bug
Following the instructions at https://hermes.informal.systems/documentation/commands/upgrade/test.html I've found an issue when Hermes should waits for the reference chain
bitcanna-dev-1
(ibc-0 in the example) to halt and then performs the upgrade for client 07-tendermint-0 onosmosis-dev-1
(ibc-1 at the Hermes doc)Version
I run it in Darwin arm64 M1
Steps to Reproduce
Run two chains and connect it by IBC; make some IBC TX in both senses, relaying them with Hermes.
Version of chain's daemons are:
Osmosis:
BitCanna:
I want upgrade
bitcanna-dev-1
tobitcanna-dev-2
keeping07-tendermint-0
working on both chains (same ClientID in both)I make the IBC upgrade proposal:
Proposal 2 is created & passed: Halt-height is
2705
Then I start the Hermes handler (before halt-height) (tested also passed the halt-height):
$ hermes upgrade client --host-chain osmosis-dev-1 --client 07-tendermint-0 --upgrade-height 2705
Output when the halt-height is reached:
At Osmosis-dev-1:
Really is updated in the host chain but not changed to revision 2 (bitcanna-dev-2) (the desired effect)
The first idea it comes to my mind is that issue is here:
latest height revision number must match chain id revision number (1 != 2)
.Acceptance Criteria
For Admin Use
The text was updated successfully, but these errors were encountered: