You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting this issue. I was able to reproduce it in OCP 4.16.3 with package "amq-broker-rhel8" which also owns same CRD with different versions. A fix is in progress right now.
greyerof
added a commit
to greyerof/certsuite
that referenced
this issue
Nov 28, 2024
As stated in issue
redhat-best-practices-for-k8s#2593 ,
the test case operator-single-crd-owner might produce false positives.
The original implementation didn't handle cases where a single CRD name
can have more than one version.
As stated in issue
#2593 ,
the test case operator-single-crd-owner might produce false positives.
The original implementation didn't handle cases where a single CRD name
can have more than one version.
When the ClusterServiceVersion contains multiple versions of the same CustomReseourceDefinition the test operator-single-crd-owner fails because counts an owner for each CustomReseourceDefinition version, i.e. ActiveMQArtemis CRD versions in https://github.com/artemiscloud/activemq-artemis-operator/blob/1.2.7/bundle/manifests/activemq-artemis-operator.clusterserviceversion.yaml
The text was updated successfully, but these errors were encountered: