Scorecard olm-crds-have-resources-test failing when the owned is in the CSV

[camilamacedo86]

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

[camilamacedo86]

Also, see that this checks are not tested: #4564

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[camilamacedo86]

/lifecycle frozen