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

API failed to restart spiderpool controller, reporting error pods "spiderpool-controller-797c94645b-c6jp8" not found #3650

Open
github-actions bot opened this issue Jun 24, 2024 · 2 comments
Assignees

Comments

@github-actions
Copy link

action url: https://github.com/spidernet-io/spiderpool/actions/runs/9651692589

@ty-dc ty-dc changed the title Night CI 2024-06-24: Failed API failed to restart spiderpool controller, reporting error pods "spiderpool-controller-797c94645b-c6jp8" not found Jun 25, 2024
@ty-dc
Copy link
Collaborator

ty-dc commented Jun 25, 2024

  now time: 2024-06-24T20:32:12.48040245Z, restart spiderpool controller 
  failed to DeletePodList
  [FAILED] Unexpected error:
      <*errors.StatusError | 0xc00042b540>: 
      pods "spiderpool-controller-797c94645b-c6jp8" not found
      {
          ErrStatus: {
              TypeMeta: {Kind: "", APIVersion: ""},
              ListMeta: {
                  SelfLink: "",
                  ResourceVersion: "",
                  Continue: "",
                  RemainingItemCount: nil,
              },
              Status: "Failure",
              Message: "pods \"spiderpool-controller-797c94645b-c6jp8\" not found",
              Reason: "NotFound",
              Details: {
                  Name: "spiderpool-controller-797c94645b-c6jp8",
                  Group: "",
                  Kind: "pods",
                  UID: "",
                  Causes: nil,
                  RetryAfterSeconds: 0,
              },
              Code: 404,
          },
      }
  occurred
  In [It] at: /home/runner/work/spiderpool/spiderpool/test/e2e/reclaim/reclaim_test.go:570 @ 06/24/24 20:32:12.521
  < Exit [It] a dirty IP record (pod name is wrong or containerID is wrong) in the IPPool should be auto clean by Spiderpool - 

@ty-dc
Copy link
Collaborator

ty-dc commented Jun 25, 2024

The pod has been restarted successfully, but the old pod name is still being used, which is not what I expected.

kube-system          spiderpool-controller-6f7449b998-g7dlt                         0/1     Running       0          3s      172.18.0.3      spiderpool0624201227-control-plane   <none>           <none>            app.kubernetes.io/component=spiderpool-controller,app.kubernetes.io/instance=spiderpool,app.kubernetes.io/name=spiderpool,pod-template-hash=6f7449b998
kube-system          spiderpool-controller-6f7449b998-nhnfq                         0/1     Running       0          3s      172.18.0.2      spiderpool0624201227-worker          <none>           <none>            app.kubernetes.io/component=spiderpool-controller,app.kubernetes.io/instance=spiderpool,app.kubernetes.io/name=spiderpool,pod-template-hash=6f7449b998

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant