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

Upgrade from 2.7.7 to 2.8.4 causes heartbeat to ping non existing leader #11718

Open
slonka opened this issue Oct 9, 2024 · 0 comments
Open
Labels
kind/bug A bug kind/service-review Service review issue triage/needs-reproducing Someone else should try to reproduce this triage/pending This issue will be looked at on the next triage meeting

Comments

@slonka
Copy link
Contributor

slonka commented Oct 9, 2024

What happened?

Reported via slack.

2024-10-08T16:47:56.595Z	INFO	intercp.catalog.heartbeat	could not send a heartbeat to a leader. It's likely due to leader change	{"instanceId": "kuma-control-plane-6fd8cc445b-vzd77-a741", "ready": true, "leaderAddress": "X", "cause": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp X:5683: i/o timeout\""}

It looks like the leader ip it is trying to hit never existed (X)

FYI @healthy-pod @sentinelleader

@slonka slonka added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this kind/service-review Service review issue labels Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug kind/service-review Service review issue triage/needs-reproducing Someone else should try to reproduce this triage/pending This issue will be looked at on the next triage meeting
Projects
None yet
Development

No branches or pull requests

1 participant