-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
Pipelines 1.19.0
-
False
-
-
False
-
-
-
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):
