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

CSV is in pending state on OCP 4.5 with the new bundles of catalogSource #1833

Closed
prafull01 opened this issue Oct 26, 2020 · 2 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@prafull01
Copy link

Bug Report

What did you do?
I am moving the my OLM bundle to the new bundle which has been introduced from OCP 4.5 version. The migration steps are explainer here:
https://redhat-connect.gitbook.io/certified-operator-guide/appendix/bundle-maintenance-after-migration

What did you expect to see?
I am able to migrate the bundle and create the catalogSource from it. Once installation my operator should come into Succeeded state

What did you see instead? Under which circumstances?
Once, I install the operator from catalogSource, the service account creation is not happening.
The CSV status throws this error:

    - group: ""
      kind: ServiceAccount
      message: Service account does not exist
      name: k8s-triliovault
      status: NotPresent
      version: v1

When I already have a service account, it will throw different error related to policies:

     - group: rbac.authorization.k8s.io
        kind: PolicyRule
        message: cluster rule:{"verbs":["use"],"apiGroups":["security.openshift.io"],"resources":["securitycontextconstraints"],"resourceNames":["privileged"]}
        status: NotSatisfied
        version: v1
      group: ""
      kind: ServiceAccount
      message: Policy rule not satisfied for service account
      name: k8s-triliovault
      status: PresentNotSatisfied
      version: v1

Is there something on the CSV side also changed? I am not able to understand why it is happening?

Environment

  • operator-lifecycle-manager version:
  • Kubernetes version information:
  • Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

Environment

  • operator-lifecycle-manager version:

quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0258562a0732798f4cb3f34d3162bcbd06b7710b21882d067c9dc067b4e15b5b

  • Kubernetes version information:
prafull@EMPID18004:~/go/src/github.com/trilioData/k8s-triliovault$ kubectl get nodes
NAME                                                          STATUS   ROLES    AGE   VERSION
ajay-nlp67-master-0.c.amazing-chalice-243510.internal         Ready    master   8d    v1.18.3+08c38ef
ajay-nlp67-master-1.c.amazing-chalice-243510.internal         Ready    master   8d    v1.18.3+08c38ef
ajay-nlp67-master-2.c.amazing-chalice-243510.internal         Ready    master   8d    v1.18.3+08c38ef
ajay-nlp67-worker-a-xtvsm.c.amazing-chalice-243510.internal   Ready    worker   8d    v1.18.3+08c38ef
ajay-nlp67-worker-b-6cnfm.c.amazing-chalice-243510.internal   Ready    worker   8d    v1.18.3+08c38ef
ajay-nlp67-worker-c-8hzbm.c.amazing-chalice-243510.internal   Ready    worker   8d    v1.18.3+08c38ef
  • Kubernetes cluster kind:
    OCP 4.5
@prafull01
Copy link
Author

/kind bug

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 26, 2020
@prafull01
Copy link
Author

The issue was in our bundle, hence closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants