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

Simulator raises an error log when delete a scheduled pod #320

Open
196Ikuchil opened this issue Aug 13, 2023 · 4 comments
Open

Simulator raises an error log when delete a scheduled pod #320

196Ikuchil opened this issue Aug 13, 2023 · 4 comments
Assignees
Labels
area/simulator Issues or PRs related to the simulator. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@196Ikuchil
Copy link
Contributor

The simulator raises an error log like below when you delete a scheduled pod.
This issue is not critical and does not affect the simulation.

E0813 19:03:12.323322   53964 storereflector.go:137] failed to update the pod with retry to record store: get pod:
    sigs.k8s.io/kube-scheduler-simulator/simulator/scheduler/storereflector.(*reflector).storeAllResultToPodFunc.func1.1
        /Users/i196/go_project/kube-scheduler-simulator/simulator/scheduler/storereflector/storereflector.go:93
  - pods "pod-5r78g" not found

/kind bug
/area simulator

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/simulator Issues or PRs related to the simulator. labels Aug 13, 2023
@sanposhiho
Copy link
Member

/kind cleanup
/remove-kind bug

as it's minor.

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/bug Categorizes issue or PR as related to a bug. labels Dec 10, 2023
@YTGhost
Copy link

YTGhost commented Dec 10, 2023

/assign

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 9, 2024
@sanposhiho
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/simulator Issues or PRs related to the simulator. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

No branches or pull requests

5 participants