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

Failure when creating operator-backed resources


    • No
    • ODC Sprint 3245
    • 1
    • Rejected
    • False
    • Hide



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

      Description of problem:

      In the developer sandbox, the happy path to create operator-backed resources is broken.
      Users can only work on their assigned namespace. When doing so, and attempting to create an Operator-backed resource from the Developer console, the user interface switches inadvertendly the working namespace from the user's to the `openshift` one. The console shows an error message when the user clicks the "create" button.

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


      How reproducible:


      Steps to Reproduce:

      1. Login to the Developer Sandbox
      2. Choose the Developer view
      3. Click Add+ -> Developer Catalog -> Operator Backed
      4. Filter by "integration"
      5. Notice the working namespace is still the user's one. 
      6. Select "Integration" (Camel K operator)
      7. Click "Create"
      8. Notice the working namespace has switched to `openshift`
      9. Notice the custom resource in YAML view includes `namespace: openshift`
      10. Click "Create"

      Actual results:

      An error message shows: "Danger alert:An error occurredintegrations.camel.apache.org is forbidden: User "bmesegue" cannot create resource "integrations" in API group "camel.apache.org" in the namespace "openshift""

      Expected results:

      On step 8, the working directory should remain the user's one
      On step 9, in the YAML view, the namespace should be the user's one, or none.
      After step 10, the creation process should trigger the creation of a Camel K integration.

      Additional info:


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