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

0.46 - Monitoring connection failure during channel handshake #920

Closed
lumtis opened this issue Aug 5, 2022 · 4 comments · Fixed by #919
Closed

0.46 - Monitoring connection failure during channel handshake #920

lumtis opened this issue Aug 5, 2022 · 4 comments · Fixed by #919

Comments

@lumtis
Copy link
Contributor

lumtis commented Aug 5, 2022

Describe the bug
Get following error during channel handshake

 ERROR ThreadId(40) send_tx_with_account_sequence_retry{id=orbit-1}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call failed with status: status: Unknown, message: "codespace monitoringp code 3: invalid version: got: , expected monitoring-1: channel open try callback failed: failed to execute message; message index: 1", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "36"} }
2022-08-05T07:44:48.606940Z ERROR ThreadId(01) failed ChanOpenTry ChannelSide { chain: BaseChainHandle { chain_id: ChainId { id: "orbit-1", version: 1 }, runtime_sender: Sender { .. } }, client_id: ClientId("07-tendermint-0"), connection_id: ConnectionId("connection-0"), port_id: PortId("monitoringp"), channel_id: None, version: Some(Version("monitoring-1")) }: failed during a transaction submission step to chain 'orbit-1': gRPC call failed with status: status: Unknown, message: "codespace monitoringp code 3: invalid version: got: , expected monitoring-1: channel open try callback failed: failed to execute message; message index: 1", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "36"} }
2022-08-05T07:44:50.135974Z ERROR ThreadId(40) send_tx_with_account_sequence_retry{id=orbit-1}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call failed with status: status: Unknown, message: "codespace monitoringp code 3: invalid version: got: , expected monitoring-1: channel open try callback failed: failed to execute message; message index: 1", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "37"} }
2022-08-05T07:44:50.136034Z ERROR ThreadId(01) failed ChanOpenTry ChannelSide { chain: BaseChainHandle { chain_id: ChainId { id: "orbit-1", version: 1 }, runtime_sender: Sender { .. } }, client_id: ClientId("07-tendermint-0"), connection_id: ConnectionId("connection-0"), port_id: PortId("monitoringp"), channel_id: None, version: Some(Version("monitoring-1")) }: failed during a transaction submission step to chain 'orbit-1': gRPC call failed with status: status: Unknown, message: "codespace monitoringp code 3: invalid version: got: , expected monitoring-1: channel open try callback failed: failed to execute message; message index: 1", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "37"} }

Potentially Hermes 0.15 doesn't support IBC v5

To Reproduce
Steps to reproduce the behavior:

  1. cd localned
  2. python3 start_spn.py
  3. python3 run_incentivized.py
@lumtis
Copy link
Contributor Author

lumtis commented Aug 5, 2022

We need to return module version in OnChanOpenInit and OnChanOpenTry
https://github.com/cosmos/ibc-go/blob/v5.0.0-beta1/modules/apps/transfer/ibc_module.go

@lumtis lumtis linked a pull request Aug 5, 2022 that will close this issue
@lumtis
Copy link
Contributor Author

lumtis commented Aug 5, 2022

Fix in #919

@aljo242
Copy link
Contributor

aljo242 commented Aug 8, 2022

Good to close?

@lumtis
Copy link
Contributor Author

lumtis commented Aug 9, 2022

Yes, the issue actually doesn't close automatically when the attached branch is not merge on the base branch

@lumtis lumtis closed this as completed Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants