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

Failed to complete action : kubescapeScan #238

Open
zhuw726 opened this issue Aug 21, 2024 · 4 comments
Open

Failed to complete action : kubescapeScan #238

zhuw726 opened this issue Aug 21, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@zhuw726
Copy link

zhuw726 commented Aug 21, 2024

Description

Error log as below, looks like it's timeout issue, please help to advice how to configure that.

{"level":"error","ts":"2024-08-21T01:14:01Z","msg":"failed to complete action","command":"kubescapeScan","wlid":"wlid://cluster-arn-aws-eks-us-west-2-AWSACCOUNT-cluster-CLUSTERNAME/namespace-NAMESPACE/deployment-APPLICATION009","error":"http: read on closed response body"}

Environment

OS: AmazonLinux2
Version: 1.20.1

Steps To Reproduce

helm repo add kubescape https://kubescape.github.io/helm-charts/ ; 
helm repo update ; 
helm upgrade --install kubescape kubescape/kubescape-operator -n kubescape --create-namespace --set clusterName=`kubectl config current-context` --set capabilities.continuousScan=enable --set kubevuln.verbose=true

Expected behavior

No error appear.

Actual Behavior

Error log as below:

{"level":"error","ts":"2024-08-21T01:14:01Z","msg":"failed to complete action","command":"kubescapeScan","wlid":"wlid://cluster-arn-aws-eks-us-west-2-AWSACCOUNT-cluster-CLUSTERNAME/namespace-NAMESPACE/deployment-APPLICATION009","error":"http: read on closed response body"}

Additional context

@zhuw726 zhuw726 added the bug Something isn't working label Aug 21, 2024
@mgalesloot
Copy link

mgalesloot commented Sep 6, 2024

Got the same issue with kubescape 1.21.1 on k3s.

operator-5bb4c47859-9dqjr operator {"level":"error","ts":"2024-09-06T12:31:37Z","msg":"failed to complete action","command":"kubescapeScan","wlid":"wlid://cluster-k3s/namespace-","error":"http: read on closed response body"} operator-5bb4c47859-9dqjr operator {"level":"error","ts":"2024-09-06T12:33:40Z","msg":"failed to complete action","command":"kubescapeScan","wlid":"","error":"http: read on closed response body"}

@TorstenD-SAP
Copy link

Same issue with 1.21.2

NAME            NAMESPACE       REVISION        UPDATED                                         STATUS          CHART                           APP VERSION
kubescape       kubescape       2               2024-09-09 08:39:42.583287923 +0200 CEST        deployed        kubescape-operator-1.21.2       1.21.2
{"level":"info","ts":"2024-09-11T11:00:33Z","msg":"restAPI receivedCommands: {\"commands\":[{\"commandName\":\"kubescapeScan\",\"jobTracking\":{\"timestamp\":\"0001-01-01T00:00:00Z\"}}]}"}
{"level":"error","ts":"2024-09-11T11:00:33Z","msg":"failed to complete action","command":"kubescapeScan","wlid":"","error":"http: read on closed response body"}

@matthyx
Copy link
Contributor

matthyx commented Oct 1, 2024

Yes, this is tracked in our internal issue tracker, @jnathangreeg should fix it sometimes.
But this error usually doesn't prevent scans from happening... otherwise let me know and I will prioritize.

@matthyx
Copy link
Contributor

matthyx commented Nov 1, 2024

solution should be merged next week

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

No branches or pull requests

4 participants