operator-framework / operator-framework/operator-sdk
Scorecard olm-crds-have-resources-test failing when the owned is in the CSV
Open
@theishshah is already working on this.
Since Oct 4, 2021.
kind/bug
lifecycle/frozen
scorecard
- Dominant language
- Go
- Stars
- 7.7k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Report
Image: quay.io/operator-framework/scorecard-test:v1.13.0
Entrypoint: [scorecard-test olm-crds-have-resources]
Labels:
"suite":"olm"
"test":"olm-crds-have-resources-test"
Results:
Name: olm-crds-have-resources
State: fail
Errors:
Owned CRDs do not have resources specified
Log:
Loaded ClusterServiceVersion: jaeger-operator.v1.25.0
What did you do?
Run scorecard for the bundle layer.zip: operator-sdk scorecard layer/
What did you expect to see?
All tests passing succefully.
What did you see instead? Under which circumstances?
Image: quay.io/operator-framework/scorecard-test:v1.13.0
Entrypoint: [scorecard-test olm-crds-have-resources]
Labels:
"suite":"olm"
"test":"olm-crds-have-resources-test"
Results:
Name: olm-crds-have-resources
State: fail
Errors:
Owned CRDs do not have resources specified
Log:
Loaded ClusterServiceVersion: jaeger-operator.v1.25.0
Environment
$ operator-sdk version 1.13.0
$ go version (if language is Go) 1.16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.