Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-180

Clusterrolebinding is referring to wrong serviceaccount namespace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • OADP 1.0.0
    • None
    • None
    • None
    • False
    • False
    • Passed
    • 0
    • 0
    • 0
    • Untriaged
    • None

      Even after installing OADP in the openshift-migration namespace I can see the clusterolebinding is referring to the wrong sa namespace which is openshift-adp instead of openshift-migration.

      $ oc get clusterrolebinding velero-rolebinding -o yaml
      
      apiVersion: rbac.authorization.k8s.io/v1
      kind: ClusterRoleBinding
      metadata:
          labels:
          olm.owner: oadp-operator.v0.5.3
        name: velero-rolebinding
      roleRef:
        apiGroup: rbac.authorization.k8s.io
        kind: ClusterRole
        name: velero-role
      subjects:
      - kind: ServiceAccount
        name: velero
        namespace: openshift-adp
      

       

      Steps to reproduce:
      1. Install OADP in any namespace other than openshift-adp
      2. Check clusterrolebinding resource

      Expected Result:  Expecting clusterrolebinding resource to use openshift-migration namespace instead of openshift-adp

              drajds@redhat.com Deepakraj Dharmapuri Selvakumar (Inactive)
              rhn-support-prajoshi Prasad Joshi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: