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

Uninstalled Event Source results in not properly finalized dynamic controller #2

Open
zroubalik opened this issue Jul 16, 2020 · 14 comments
Assignees
Labels
bug Something isn't working triage/accepted Issues which should be fixed (post-triage)

Comments

@zroubalik
Copy link
Contributor

If we create a new Event Source, ie. we install Kafka Sources or AWS SQS Source, the parent controller successfully creates a new dynamic controller for this particular Source. But if we unistall this Source, the created dynamic controller is not properly finalized/destroyed. This results in error messages in the log:

E0716 16:57:18.095520       1 reflector.go:382] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:125: Failed to watch *v1.Source: the server could not find the requested resource

This part of the code is probably not properly called:
https://github.com/zroubalik/autoscaler-keda/blob/85186c0c257126f6aa71fac9b26f9b252210e523/pkg/reconciler/crd/reconciler.go#L111-L119

@zroubalik zroubalik added the bug Something isn't working label Jul 23, 2020
@github-actions
Copy link

github-actions bot commented Nov 4, 2020

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2020
@zroubalik
Copy link
Contributor Author

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2020
@aavarghese
Copy link
Contributor

/assign

@aavarghese
Copy link
Contributor

FYI: I see this error in the logs in BOTH eventing-autoscaler-keda's contoller controller-xxx -n eventing-autoscaler-keda AND also in knative-eventing's controller eventing-controller-xxx -n knative-eventing when the CRD is uninstalled.

That expected?

cc: @zroubalik

@zroubalik
Copy link
Contributor Author

@aavarghese I don't think this is expected. We should talk to some folks familiar with that part of Eventing, maybe @nachocano?

CC @lionelvillard any suggestion?

@lionelvillard
Copy link
Contributor

interesting. I've seen this error before in core eventing, can't find the issue.

@nachocano any ideas?

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2021
@lionelvillard
Copy link
Contributor

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2021
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2021
@zroubalik zroubalik reopened this Jun 28, 2021
@lionelvillard
Copy link
Contributor

/remove-lifecycle stale

@lionelvillard lionelvillard reopened this Jul 29, 2021
@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 29, 2021
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2021
@aavarghese
Copy link
Contributor

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2021
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2022
@zroubalik zroubalik reopened this Feb 28, 2022
@pierDipi
Copy link
Member

/remove-lifecycle stale
/triage accepted

@pierDipi pierDipi reopened this Mar 31, 2022
@knative-prow knative-prow bot added triage/accepted Issues which should be fixed (post-triage) and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants