We had a customer issue that was caused by incorrect permissions for assisted installer.  While the end fix was on the back end, the UI still did not handle the situation in the best manner.  A 403 error was reported by the API call to assisted installer.  We will let the assisted installer team work on the logic around how/why the 403 error was sent to us instead of something more meaningful.

The overall fix was to add permissions to the new user that the cluster was transferred to and update the external cluster ID to the proper value in the back end tables.

However, the question has been asked if we should show a 403 error message from the AI api call on the front end so the user knows there is an issue?

 - Figure out if an error message is appropriate

• If so, implement a proper message

Procedure the customer used to create the issue.

1) Build a bare metal OCP cluster using Assisted Installer

2) Register the cluster with OCM UI

3) Using the UI, initiate a transfer to another user that does not have permissions to use assisted installer (not exactly sure what these would entail as the back end team took care of this).

4) Now go to clusters/list as the user the cluster was transferred to after the transfer is complete, find the cluster and try to click into details for the cluster

5) A spinner will show indefinitetly and the page will never load or show an error message.  Looking at the dev-tools, there will be several 403 errors and the subscription api call will never return anything.