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

PodTemplate not found #868

Closed
salaxander opened this issue Sep 21, 2023 · 2 comments · Fixed by #875
Closed

PodTemplate not found #868

salaxander opened this issue Sep 21, 2023 · 2 comments · Fixed by #875
Labels
bug Something isn't working

Comments

@salaxander
Copy link
Contributor

salaxander commented Sep 21, 2023

Issue seen by user of the AKS managed addon:

{
  "level": "error",
  "ts": 1694539328.40113,
  "msg": "Reconciler error",
  "controller": "imagejob-controller",
  "object": {
    "name": "imagejob-slchb",
    "namespace": "kube-system"
  },
  "namespace": "kube-system",
  "name": "imagejob-slchb",
  "reconcileID": "4caba556-ab6c-431a-81c8-36a3aa79cbf9",
  "error": "reconcile running: PodTemplate \"imagejob-slchb\" not found",
  "stacktrace": "sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:329\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:235"
}

Started immediately after startup of the Eraser controller.

Environment:

  • Eraser version: v1.2.1
  • Kubernetes version: (use kubectl version): v1.25.11
@salaxander salaxander added the bug Something isn't working label Sep 21, 2023
@pargall
Copy link

pargall commented Sep 25, 2023

Saw the same issue on my AKS clusters starting around 9/12, running the same versions mentioned above. I found restarting the deployment(kubectl -n kube-system rollout restart deployment/eraser-controller-manager) mitigated the issue for me.

@mgacuzana
Copy link

Restarting the controller deployment enabled the new controller to kick off a new ImageJob.

I still see the same error in the logs, for the exact same ImageJob as the previous controller (imagejob-slchb), so it doesn't appear to completely mitigate the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants