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

Topology get Error Pod message #767

Open
Cookiery opened this issue Jan 27, 2025 · 3 comments
Open

Topology get Error Pod message #767

Cookiery opened this issue Jan 27, 2025 · 3 comments
Labels
bug Something isn't working priority/important-longterm P2 Important over the long term,but may not be staffed and/or may need multiple releases to complete
Milestone

Comments

@Cookiery
Copy link
Contributor

Cookiery commented Jan 27, 2025

What happened?

Namespace Page

  1. Click ReplicaSet and then click Pod;
  2. It triggers two requests
  3. The Error is reported as follows.

Image

Payload:
Image

Response:
Image

The true request payload:
Image

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

Karpor version

$ karpor -V
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

@elliotxx
Copy link
Collaborator

elliotxx commented Jan 27, 2025

@Cookiery This should be caused by the inconsistency between the actual status of ES and k8s. When the resources in the cluster have been deleted, but the data in ES has not been deleted yet, this error message will appear; Usually, it is caused by the karpor-syncer not synchronizing and deleting events properly.
I need to think about how to solve this problem 🤔

@elliotxx elliotxx added bug Something isn't working priority/important-longterm P2 Important over the long term,but may not be staffed and/or may need multiple releases to complete area/syncer labels Jan 27, 2025
@elliotxx elliotxx added this to the v0.7.0 milestone Jan 27, 2025
@github-actions github-actions bot mentioned this issue Jan 27, 2025
37 tasks
@Cookiery
Copy link
Contributor Author

Could you reproduce the question?

@elliotxx
Copy link
Collaborator

@Cookiery It's occasional in my local, and I'm trying to reproduce it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority/important-longterm P2 Important over the long term,but may not be staffed and/or may need multiple releases to complete
Projects
None yet
Development

No branches or pull requests

2 participants