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

Healthcheck fails on all nodes due to IBC-Go module not found #3880

Closed
5 tasks
freak12techno opened this issue Mar 11, 2024 · 2 comments · Fixed by #3888
Closed
5 tasks

Healthcheck fails on all nodes due to IBC-Go module not found #3880

freak12techno opened this issue Mar 11, 2024 · 2 comments · Fixed by #3888
Assignees
Labels
A: bug Admin: something isn't working
Milestone

Comments

@freak12techno
Copy link
Contributor

Summary of Bug

On Hermes startup (or on invoking hermes health-check manually), it spawns a lot of messages on all of the chains I have in config that the healthcheck failed for this chain because it allegedly doesn't have IBC-Go module (although it's not true), for example on Cosmos Hub:

Mar 11 17:24:18 monitoring-logging hermes[925785]: 2024-03-11T16:24:18.679278Z  WARN ThreadId(22) 
health_check{chain=cosmoshub-4}: reason: compatibility check failed for chain 'cosmoshub-4' at
'http://rpc.cosmos.quokkastake.io:9090/': IBC-Go module version not found, required >=4.1.1, <9

If you go into REST's /node_info (example on my node: https://api.cosmos.quokkastake.io/node_info), it'll show there's ibc-go dependency in build_deps:

24	"github.com/cosmos/ibc-go/v4@v4.4.2"

although it's not processed correctly.
I am not sure yet why this keeps happening, wonder if it might happen because the dependency itself has the v4 suffix here?

This doesn't seem to affect anything, yet having more warning messages that are misleading is somewhat annoying.

Version

v1.8.1

Steps to Reproduce

Run hermes health-check or restart Hermes.

Acceptance Criteria

???


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@romac romac self-assigned this Mar 12, 2024
@romac romac added the A: bug Admin: something isn't working label Mar 12, 2024
@romac romac added this to the 1.8.2 milestone Mar 12, 2024
@romac
Copy link
Member

romac commented Mar 13, 2024

@freak12techno Thanks for reporting this! The issue should be fixed in Hermes v1.8.2 if you want to give it a try

@freak12techno
Copy link
Contributor Author

@romac already did, and yeah, it fixed it, thanks!
(I still have some other issues, will likely report it separately, but this one seems to be gone)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: bug Admin: something isn't working
Projects
Status: ✅ Done
2 participants