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

Allow version compatibility between chains upgrade from v8.x to v9.x #7846

Closed
4 tasks
mmsqe opened this issue Jan 15, 2025 · 3 comments
Closed
4 tasks

Allow version compatibility between chains upgrade from v8.x to v9.x #7846

mmsqe opened this issue Jan 15, 2025 · 3 comments

Comments

@mmsqe
Copy link
Contributor

mmsqe commented Jan 15, 2025

Summary

relayer and source chain bump to v9.x, while destination chain stays at v8.x

Problem Definition

relayer failed to query clients with no concrete type registered for type URL /ibc.lightclients.localhost.v2.ClientState against interface *exported.ClientState error unless both chains bump to v0.9.x

Use cases

allow less breaking upgrades

Proposal

keep legacy localhost RegisterInterfaces for relayer


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
  • Estimate provided
@gjermundgaraba
Copy link
Contributor

I might be missing some context on this, but it seems like this is a problem with the relayer? Which relayer is giving this error?

@mmsqe
Copy link
Contributor Author

mmsqe commented Jan 15, 2025

Yes, no issue if relayer and chains bump to v9.0.2, to avoid bump the other chain, I need add back the legacy RegisterInterfaces for relayer.

@mmsqe
Copy link
Contributor Author

mmsqe commented Jan 15, 2025

Closing, since add back in relayer is good enough.

@mmsqe mmsqe closed this as completed Jan 15, 2025
@mmsqe mmsqe changed the title Allow flexible version compatibility between chains upgrade from v0.8.x to v0.9.x Allow version compatibility between chains upgrade from v8.x to v9.x Jan 23, 2025
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