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

Error logs seen on the zone CP after federation #11768

Open
jijiechen opened this issue Oct 12, 2024 · 1 comment
Open

Error logs seen on the zone CP after federation #11768

jijiechen opened this issue Oct 12, 2024 · 1 comment
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@jijiechen
Copy link
Member

What happened?

By following this guide, https://kuma.io/docs/2.8.x/guides/federate/ we can federate a zone CP to a global CP.

After federating to the global CP, I can see the following log entries. But the policies flowed well from global to zone and vice versa; I can also see the zone shown as "online" on the GUI.

We need to analyze whether this is a doc issue or a defect in the product.

2024-10-11T09:24:26.222Z        ERROR   kds-zone        failed to flush zone status     {"zone": "zone-fed", "error": "Resource not found: type=\"Zone\" name=\"zone-fed\" mesh=\"\""}
2024-10-11T09:24:26.225Z        INFO    defaults        ensuring Zone resource exists   {"name": "zone-fed"}
2024-10-11T09:24:26.225Z        INFO    defaults        detected Zone resource with different name than Zone CP name. Deleting. This might happen if you change the name of the Zone CP      {"name": "zone-fed"}
@jijiechen jijiechen added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Oct 12, 2024
@lukidzi lukidzi added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Oct 21, 2024
@lukidzi
Copy link
Contributor

lukidzi commented Oct 21, 2024

Triage: there might be some race between callbacks. We should take a look at it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

2 participants