-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
None
Description
User has moved to the cluster archives page and came back to the cluster list page. In the Cluster list page, the user has enabled the filter "view only my cluster" and on clicking any listed clusters, the cluster details page shows a warning associated with the cluster name. The tool tip message shows that
An error occurred when fetching clusters: ACCT-MGMT-11: Account with ID 2Hzjt5T8ncUxnS1BuPF5Fbtyl99 denied access to perform get on Subscription with HTTP call GET /api/accounts_mgmt/v1/subscriptions/2Hzjt5T8ncUxnS1BuPF5Fbtyl99
This seems to be wrong behavior and not able to come out of this situation even after clearing session or browser cookies.
Note: The above warning hasn't shown when a user opens the cluster details page from the cluster list without the filter "view only my cluster" on.
Steps to reproduce:
- Launch OCM staging.
- Go to the cluster archives page.
- Go to the cluster list page and enable the filter "view only my cluster"
- Open any of the clusters and see the behavior.
- Perform edit display name and see the behavior.
Actual results:
Once user comes back from the Cluster archives page to cluster list page with a "view only my cluster" filter is on,
1. A wrong warning with the below message has shown in the cluster details page.
An error occurred when fetching clusters: ACCT-MGMT-11: Account with ID 2Hzjt5T8ncUxnS1BuPF5Fbtyl99 denied access to perform get on Subscription with HTTP call GET /api/accounts_mgmt/v1/subscriptions/2Hzjt5T8ncUxnS1BuPF5Fbtyl99{_}
{_}2. If a user tries to edit the display name of the cluster , it will fail and throw a similar error message.
It looks like the issue is related to the wrong subscription id associated with urls while clicking the details of the cluster.
Expected results:
Once user comes back from the Cluster archives page to cluster list page with a "view only my cluster" filter is on,
1. No wrong warning message should be shown in the cluster details page.
2. User should successfully edit the display name of the cluster without any issue.
Attached screen capture for the same. ClusterWrongMsg.mp4