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

webhook controller has a lot of messages error messages about missing cacert #1047

Closed
chmouel opened this issue Feb 4, 2020 · 2 comments
Closed
Labels
area/API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@chmouel
Copy link
Contributor

chmouel commented Feb 4, 2020

a lot of error messages due of missing cacert have started to appears in the tektoncd-webhook pod logs, this has been happenning since we did a bump to use knative.pkg-0.12 in here tektoncd/pipeline#1894 :

{"level":"info","logger":"webhook","caller":"controller/controller.go:363","msg":"Reconcile failed. Time taken: 115.268µs.","knative.dev/traceid":"5c365bc2-40a6-4e9c-9af6-d6c96d690317","knative.dev/key":"webhook.pipeline.tekton.dev"}
{"level":"error","logger":"webhook","caller":"controller/controller.go:376","msg":"Reconcile error","error":"secret \"webhook-certs\" is missing \"ca-cert.pem\" key","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\t/workspace/tektoncd-pipeline-git/vendor/knative.dev/pkg/controller/controller.go:376\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\t/workspace/tektoncd-pipeline-git/vendor/knative.dev/pkg/controller/controller.go:362\nknative.dev/pkg/controller.(*Impl).Run.func2\n\t/workspace/tektoncd-pipeline-git/vendor/knative.dev/pkg/controller/controller.go:310"

They seem harmless and only shows up at boot time and for the webhook controller but there is quite a few of them (55) and they may look quite worrisome for the uneducated user.

/kind bug

@chmouel
Copy link
Contributor Author

chmouel commented Feb 4, 2020

oh prow parses the comments 🤦‍♂

@github-actions
Copy link
Contributor

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 Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants