Description of problem:

When users try to create a new Custom Serving Runtime, either by duplicating OOTB ones or by importing a new one or from scratch, regardless the user permissions they have.

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

(steps reported only for creating custom serving runtime by uploading a yaml file. The issue is not specific to a particular user path)

1. log in with a RHODS admin or cluster admin or dedicated admin
2. go to RHODS Dashboard > Settings > Serving Runtimes
3. click "Add serving runtime" button
4. click "Upload files" button
5. upload your custom serving runtime
6. click "Add" button

Actual results:

Request failed with status code 403

Expected results:

Runtime created with success

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

RHODS v1.29.0 RC 1

Workaround:

UPDATE

• manually create the OpenShift Role to allow dashboard service account to successfully create the Custom Serving Runtime. lferrnan@redhat.com
  • it's not ideal for customers to perform a such action affecting RHODS dashboard. Since 1.29 is not in production yet, we will rebuild

Additional info: