description

UI buttons for cluster creation, that should be disabled based on permissions, are not disabled when the backend API env' is production.

steps to reproduce

1. create an external RH account (i.e. using a non-RH email address), and make sure it doesn't have admin role
2. log in with that account to staging console: https://console.dev.redhat.com/
3. navigate to /openshift/overview and note the state of the 'Create cluster' button in the 'Red Hat OpenShift Dedicated' card
4. append ?env=production to the URL, and note the button state again
5. with the same account, switch to production console, by visiting: https://console.redhat.com/
6. navigate to /openshift/overview and note the state of the same button
7. append ?env=staging to the URL, and note the button state again

expected results

buttons should be disabled in all environment permutations.

actual result

buttons are only disabled when the UI uses the 'staging' backend API:

console.dev.redhat.com: disabled
console.dev.redhat.com / env=production: enabled
console.redhat.com: enabled
console.redhat.com / env=staging: disabled

notes

• the button noted in 'steps to reproduce' is one example, please refer to OCMUI-3165 for the full list of affected UI controls (these problems were found as a gap in the fix for OCMUI-3165)
• this might be a bug or regression with the BE service, but still needs to be verified as such
• it appears we don't do quality checks on UI production (i.e. run post deployment E2E tests), which might be the reason this bug slipped by QE