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

pac info install cmd missing repository CR

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      - Fixes the tkn-pac cli to correctly bind the --namespace/-n flag to namespace instead of kube config.
      - Fixes `install info` display template condition to view repos when there exists only one CR.
      Show
      - Fixes the tkn-pac cli to correctly bind the --namespace/-n flag to namespace instead of kube config. - Fixes `install info` display template condition to view repos when there exists only one CR.
    • Bug Fix
    • Done

      Description of problem:

      opc pac info install cmd not showing repository CR for GitLab on user-created namespaces.

      Steps to Reproduce

      Install openshift-pipelines 1.17.1.

      Configure PAC via GitLab on user-created namespace and run opc pac info install 

      Actual results:

      Pipelines as Code:
       Install Version: v0.29.1
       Install Namespace: openshift-pipelines

      Expected results:

      Pipelines as Code:
       Install Version: v0.29.1
       Install Namespace: openshift-pipelines

      Repositories CR: 2
         Namespace   URL
       - ns1         https://anurl.com
       - ns2         https://somewhere.com

      Reproducibility (Always/Intermittent/Only Once):

      Always

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

      opc pac info install -n releasetest-qdlq8 
Error: Couldn't get kubeConfiguration namespace: stat releasetest-qdlq8: no such file or directory
      kubectl get repo -A 
NAMESPACE NAME URL SUCCEEDED REASON STARTTIME COMPLETIONTIME
releasetest-qdlq8 release-tests-fork-91530854 https://gitlab.com/test2602035/release-tests-fork-91530854 True Succeeded 171m 170m

              rh-ee-akpant Akshay Pant
              rhn-support-sselvan Sri Vignesh Selvan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: