You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"capability not found for existing channel, portID (%s) channelID (%s)", portID, channelID,
)
}
error: failed to execute message; message index: 1: channel handshake open try failed: could not create channel capability for port ID transfer and channel ID ibc1xfer177: module: ibc, name: capabilities/ports/transfer/channels/ibc1xfer177/key: capability name already taken
Version
This is seen with v0.40.0-rc0 but I believe it will fail also with latest.
Steps to Reproduce
I used Rust relayer CLIs from a private branch. The stargate-4 Go rly CLIs don't seem to work, however if you alter the channel-tx.go:CreateChannelStep() function to init both ends, the channel handshake will not finish.
Haven't looked at the SDK tests but probably adding one there is the simplest.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary of Bug
If a channel is in
Init
state,ChannOpenTry
Tx fails here:cosmos-sdk/x/ibc/core/04-channel/keeper/handshake.go
Lines 217 to 222 in ed9fc05
error:
failed to execute message; message index: 1: channel handshake open try failed: could not create channel capability for port ID transfer and channel ID ibc1xfer177: module: ibc, name: capabilities/ports/transfer/channels/ibc1xfer177/key: capability name already taken
Version
This is seen with
v0.40.0-rc0
but I believe it will fail also with latest.Steps to Reproduce
I used Rust relayer CLIs from a private branch. The
stargate-4
Go rly CLIs don't seem to work, however if you alter thechannel-tx.go:CreateChannelStep()
function to init both ends, the channel handshake will not finish.Haven't looked at the SDK tests but probably adding one there is the simplest.
For Admin Use
The text was updated successfully, but these errors were encountered: