search

kubernetes-sigs / wg-policy-prototypes

A place for policy work group related proposals and prototypes.
Apache License 2.0
64 stars 39 forks source link

kube-bench-adapter Job pending in Error State #94

Closed fjogeleit closed 2 years ago

fjogeleit commented 2 years ago

On my local K3s Cluster the Jobs pending in Error state with the following logs:

Found (1) pods
pod (kube-bench-2zd4m) - "Pending"
Found (1) pods
pod (kube-bench-2zd4m) - "Succeeded"
failed to run job of kube-bench: invalid character 'A' looking for beginning of value

Kubernetes Version: v1.21.6+k3s1

mritunjaysharma394 commented 2 years ago

/assign @mritunjaysharma394

mirtov-alexey commented 2 years ago

in my case the cronjob just hangs in the state: kubectl describe cronjob policyreport ─╯ Name: policyreport Namespace: default Labels: <none> Annotations: <none> Schedule: 0 * * * * Concurrency Policy: Allow Suspend: False Successful Job History Limit: 3 Failed Job History Limit: 1 Starting Deadline Seconds: <unset> Selector: <unset> Parallelism: <unset> Completions: <unset> Pod Template: Labels: <none> Service Account: clusterpolicyreport Containers: policyreport: Image: mritunjay394/policyreport Port: <none> Host Port: <none> Environment: <none> Mounts: <none> Volumes: <none> Last Schedule Time: <unset> Active Jobs: <none> Events: <none>

and job is not created

at the same time, if I try to create just a pod with image image: mritunjay394/policyreport, then I also get an error invalid character 'A' looking for beginning of value

@mritunjaysharma394

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/wg-policy-prototypes/issues/94#issuecomment-1215099430): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.