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

Pipelines operator: Error on creating repository resource and populating webhook.secret

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • Pipelines 1.19.0
    • UI
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      1) Login to OCP console
      2) Click on pipelines link, move to repostory tab
      3) Create repo.
      4) Use internal/ self hosted git repo url, on clciking save it throws the error and remains on same page.
      5) If we manually go back to repo page, repository seems to have created.
      6) Issue doesn't happen if I use public github repo

      Show
      1) Login to OCP console 2) Click on pipelines link, move to repostory tab 3) Create repo. 4) Use internal/ self hosted git repo url, on clciking save it throws the error and remains on same page. 5) If we manually go back to repo page, repository seems to have created. 6) Issue doesn't happen if I use public github repo

      Description of problem:

      While trying to create repository from OCP pipelines console getting below error (attached screenshot).
      ~~~
      Danger alert:An error occurred
      b is null
      ~~~

      Although if I go back to repositories page, I can see the repo has been created.

       

      There are already reported issues in upstream for similar issues.

      [1] https://github.com/openshift-pipelines/console-plugin/issues/403

      [2] https://github.com/openshift-pipelines/console-plugin/issues/402

       

      It seems like issue only happens if we use self-hosted git repos, i used gitlab, customer is using bit-bucket. Works fine with public github repos.

       

      Workaround

      Prerequisites (if any, like setup, operators/versions): Openshift Pipelines Operator 1.19

      Steps to Reproduce

      1) Login to OCP console
      2) Click on pipelines link, move to repostory tab
      3) Create repo.
      4) Use internal/ self hosted git repo url, on clciking save it throws the error and remains on same page.
      5) If we manually go back to repo page, repository seems to have created.
      6) Issue doesn't happen if I use public github repo

       

      Actual results: Error is shown

      Expected results: Success message should be shown

      Reproducibility (Always/Intermittent/Only Once): Always

      Additional info (Such as Logs, Screenshots, etc):

       *

              Unassigned Unassigned
              rhn-support-sudnair Sudhish Nair
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: