- Notifications
You must be signed in to change notification settings - Fork 1.8k
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.scorecardIssue relates to the scorecard subcomponentIssue relates to the scorecard subcomponent
Milestone
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
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.scorecardIssue relates to the scorecard subcomponentIssue relates to the scorecard subcomponent