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

delete crd but not stop informer watch/list #84494

Closed
calmkart opened this issue Oct 29, 2019 · 4 comments
Closed

delete crd but not stop informer watch/list #84494

calmkart opened this issue Oct 29, 2019 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@calmkart
Copy link
Contributor

calmkart commented Oct 29, 2019

What happened:
when i create a crd and delete it, the kubernetes controller logs stderr
reflector.go:123] k8s.io/client-go/metadata/metadatainformer/informer.go:89: Failed to list *v1.PartialObjectMetadata: the server could not find the requested resource
again and again.
If I delete more crd, the stderr will disturb me so I can't see other information.

What you expected to happen:
if i delete a crd, the informer watch/list will stop.
controller shouldn't print error.

How to reproduce it (as minimally and precisely as possible):
test.yaml

apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: testits.calmkart.com
spec:
  group: calmkart.com
  version: v1
  names:
    kind: Testit
    plural: testits
  scope: Namespaced

kubectl apply -f test.yaml
kubectl delete -f test.yaml
then, tail the controller logs in namespace kube-system, the stderr print(about 1/s)

Anything else we need to know?:
issue79610 is like this situation, but a little different.
how to solve it?
can i help with it?

Environment:

  • Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Network plugin and version (if this is a network-related bug):
  • Others:
@calmkart calmkart added the kind/bug Categorizes issue or PR as related to a bug. label Oct 29, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Oct 29, 2019
@calmkart
Copy link
Contributor Author

/sig api-machinery

@k8s-ci-robot k8s-ci-robot added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 29, 2019
@yue9944882
Copy link
Member

issue79610 is like this situation, but a little different.

this is exactly a duplicate of #79610, am i missing anything?

@liggitt
Copy link
Member

liggitt commented Oct 29, 2019

yes, duplicate of #79610

/close

@k8s-ci-robot
Copy link
Contributor

@liggitt: Closing this issue.

In response to this:

yes, duplicate of #79610

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

No branches or pull requests

4 participants