Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add errors for metadata.annotations.olm fields to verify #168

Open
jsm84 opened this issue Oct 1, 2019 · 0 comments
Open

Add errors for metadata.annotations.olm fields to verify #168

jsm84 opened this issue Oct 1, 2019 · 0 comments

Comments

@jsm84
Copy link

jsm84 commented Oct 1, 2019

Having the following fields set in the CSV metadata will cause an operator to fail to deploy using OLM:

metadata:
  annotations:
    olm.operatorGroup: cloudera-pxs9f
    olm.operatorNamespace: cloudera
    olm.targetNamespaces: cloudera

I'm not sure why this occurs, but the actual error given by OLM (found under the installPlan) is:

status:
  conditions:
    - lastTransitionTime: '2019-10-01T18:19:47Z'
      lastUpdateTime: '2019-10-01T18:19:47Z'
      message: >-
        error generating ownerrefs for service account: cfm-operator:
        clusterserviceversions.operators.coreos.com "cfm-operator.v1.1.31" not
        found

It appears that by having these fields set, the CSV fails to get created by OLM. This is the second time I've come across this (the other instance was back in April for CrunchyData). The failure in OLM is easily reproducible by deploying an operator for which the metadata (CSV) has those fields set.

The operator-courier verify command should ideally catch this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant