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

[knative] Self-provisioner user can not access or create event sources via ODC

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • None
    • Rejected
    • ODC Sprint 3274
    • 1
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

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

      Description of problem:

      No admin users can't create event sources via ODC.
      
      See:
      
      * https://redhat-internal.slack.com/archives/CGYQL9XPG/p1745328239318089
      * https://redhat-internal.slack.com/archives/CJYKV1YAH/p1733230836302119

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

      4.18.x
      4.19.x

      How reproducible:

      Always

      Steps to Reproduce:

      1. Log in as non-admin user, who has a project assigned
      2. Try creating an event source using ODC form    

      Actual results:

      An error is shown: You do not have create access for Event Source in this project

      Expected results:

      The event source should be created without issues

      Additional info:

      We did checked that creating the Event Source from CLI works so this must be a ODC related bug:
      
      spathak@spathak-thinkpadt14sgen1:~/Downloads$ kn source ping create test-ping-source     --schedule "*/2 * * * *"     --data '{"message": "Hello world!"}'     --sink ksvc:event-display
      Ping source 'test-ping-source' created in namespace 'testing-knatice-dev'.

       

              rh-ee-lprabhu Lokananda Prabhu
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Sanket Pathak Sanket Pathak
              None
              Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: