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

ChannOpenTry Tx fails if there is an existing channel in Init state #8036

Closed
4 tasks
ancazamfir opened this issue Nov 27, 2020 · 2 comments
Closed
4 tasks

Comments

@ancazamfir
Copy link

Summary of Bug

If a channel is in Init state, ChannOpenTry Tx fails here:

capKey, found = k.scopedKeeper.GetCapability(ctx, host.ChannelCapabilityPath(portID, channelID))
if !found {
return "", nil, sdkerrors.Wrapf(types.ErrChannelCapabilityNotFound,
"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
@colin-axner
Copy link
Contributor

colin-axner commented Nov 27, 2020

fixed by #7678 (duplicate of #7605)

@ancazamfir
Copy link
Author

Oops, sorry thought I checked latest. Great it's fixed!

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

No branches or pull requests

2 participants