Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-6671

Broken secret created while starting a Pipeline

XMLWordPrintable

    • None
    • ODC Sprint 231
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when creating a Secret, the Start Pipeline model created an invalid JSON value, As a result, the Secret was unusable and the `PipelineRun` could fail. With this fix, the Start Pipeline model creates a valid JSON value for the Secret. Now, you can create valid Secrets while starting a Pipeline. (link:https://issues.redhat.com/browse/OCPBUGS-6671[OCPBUGS-6671*])
      Show
      * Previously, when creating a Secret, the Start Pipeline model created an invalid JSON value, As a result, the Secret was unusable and the `PipelineRun` could fail. With this fix, the Start Pipeline model creates a valid JSON value for the Secret. Now, you can create valid Secrets while starting a Pipeline. (link: https://issues.redhat.com/browse/OCPBUGS-6671 [ OCPBUGS-6671 *])
    • Done

      This is a clone of issue OCPBUGS-3228. The following is the description of the original issue:
      —
      While starting a Pipelinerun using UI, and in the process of providing the values on "Start Pipeline" , the IBM Power Customer (dpkshetty_rh from IBM) has tried creating credentials under "Advanced options" with "Image Registry Credentials" (Authenticaion type). When the IBM Customer verified the credentials from  Secrets tab (in Workloads) , the secret was found in broken state. Screenshot of the broken secret is attached. 

      The issue has been observed on OCP4.8, OCP4.9 and OCP4.10.

            cjerolim Christoph Jerolimov
            openshift-crt-jira-prow OpenShift Prow Bot
            Sanket Pathak Sanket Pathak
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: