Skip to content

bug: stop treating a deleted cluster as a deploy failure#487

Merged
gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:not-existing-cluster
Jul 10, 2026
Merged

bug: stop treating a deleted cluster as a deploy failure#487
gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:not-existing-cluster

Conversation

@gianlucam76

Copy link
Copy Markdown
Member

Classifier collects all ClassifierReports present in the management cluster and process them. A ClassifierReport left over from a since-deleted cluster gets treated as a hard failure on every single reconcile

Fix consists in:

  1. deployClassifier: before calling processClassifier, check whether the report's cluster still exists. If it's NotFound, skip the report instead of treating it as a failure.
  2. New background sweep: runs every 5 minutes and removes ClassifierReports whose cluster no longer exists.

…r reconcile

Classifier collects all ClassifierReports present in the management cluster and process
them. A ClassifierReport left over from a since-deleted cluster gets treated as a hard
failure on every single reconcile

Fix consists in:

1. deployClassifier: before calling processClassifier, check whether the report's cluster still exists.
If it's NotFound, skip the report instead of treating it as a failure.
2. New background sweep: runs every 5 minutes and removes ClassifierReports whose cluster no longer exists.
@gianlucam76 gianlucam76 merged commit a873a87 into projectsveltos:main Jul 10, 2026
7 checks passed
@gianlucam76 gianlucam76 deleted the not-existing-cluster branch July 10, 2026 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant