Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-2256

All pipelines getting failed after upgrading openshift-pipelines operator to v1.7.0 | Re-linking secrets to the service account fixes everything

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • Pipelines Sprint 221, Pipelines Sprint 222, Pipelines Sprint 223

      Hello Team,

      Opening this on the basis of following discussion:
      https://coreos.slack.com/archives/CSPS1077U/p1652112446006439

      The customer was using openshift-pipelines operator v1.6.2. As soon as the customer upgraded the openshift-pipelines to version 1.7.0, all pipelines began to fail with varying errors. 

      This issue got fixed after the customer re-linked the secrets to the service account.

      Commands used (for reference):

      oc secret link pipeline alliance-tas-cicd-account-pull-secret 
oc secret link pipeline tas-source-secret
oc secret link pipeline bitbucket-basic-auth-secret

# provide service account tas-cicd:pipeline to edit stuff on tas-dev project

oc policy add-role-to-user edit system:serviceaccount:tas-cicd:pipeline -n tas-dev
oc policy add-role-to-user edit system:serviceaccount:tas-cicd:pipeline -n tas-test
oc policy add-role-to-user edit system:serviceaccount:tas-cicd:pipeline -n tas-uat

      Thanks!

       

            pradkuma PRADEEP KUMAR (Inactive)
            rhn-support-kkulshre Kushagra Kulshreshtha
            Votes:
            4 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: