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

Project admins cannot see 'Pipelines' section in 'import from git' from RHOCP4 web console


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.12.z
    • Dev Console
    • Moderate
    • No
    • ODC Sprint 241
    • 1
    • Rejected
    • False
    • Hide



      This is a clone of issue OCPBUGS-15427. The following is the description of the original issue:

      Description of problem:

      As a cluster-admin, users can see pipelines section while using the `import from git` feature in the developer mode from web console.
      However if users logged in as a normal user or a project admin, they are not able to see the pipelines section.

      Version-Release number of selected component (if applicable):

      Tested in OCP v4.12.18 and v4.12.20 

      How reproducible:


      Steps to Reproduce:

      Prerequisite- Install Red Hat OpenShift pipelines operator
      1. Login as a kube-admin user from web console
      2. Go to Developer View
      3. Click on +Add
      4. Under Git Repository, open page -> Import from git
      5. Enter Git Repo URL (example git url- https://github.com/spring-projects/spring-petclinic)
      6. Check if there are 3 section : General , Pipelines , Advance options
      7. Then Login as a project admin user
      8. Perform all the steps again from step 2 to step 6

      Actual results:

      Pipelines section is not visible when logged in as a project admin. Only General and Advance options sections are visible in import from git.
      However Pipeline section is visible as a cluster-admin.

      Expected results:

      Pipelines section should be visible when logged in as a project admin, along with General and Advance options sections in import from git.

      Additional info:

      I checked by creating a separate rolebinding and clusterrolebindings to assign access for pipeline resources like below :
      $ oc create clusterrole pipelinerole1 --verb=create,get,list,patch,delete --resource=tektonpipelines,openshiftpipelinesascodes
      $ oc create clusterrole pipelinerole2 --verb=create,get,list,patch,delete --resource=repositories,pipelineruns,pipelines
      $ oc adm policy add-cluster-role-to-user pipelinerole1 user1
      $ oc adm policy add-role-to-user pipelinerole2 user1
      However, even after assigning these rolebindings/clusterrolebinsings to the users , users are not able to see the Pipelines section.

            viraj-1 Vikram Raj
            openshift-crt-jira-prow OpenShift Prow Bot
            Sanket Pathak Sanket Pathak
            0 Vote for this issue
            5 Start watching this issue