Description of problem:

This issue hits users  with a clusters huge number (~ 10k) visibility and with multiregion feature enabled. If such a user goes to cluster list page, very likely the total number of cluster will take a little to be entirely loaded in the app. But if the user don't wait for all the loading finishing and clicks ">>" to jump to the last page of the table, the number of clusters shown could be (was always in my tests) less than the page size (always 5 in my tests). In theory, as clusters loading proceeds, the number of clusters shown in the page (which in the meanwhile is not anymore the last one) should suddenly reach the page size, but instead it keep to be the same.

How reproducible:

always in my tests

Steps to Reproduce:

1. Open OCM UI staging.
2. Append in the url "?multiregion=true" (related feature flag has to be enabled too)
3. Go to the cluster list page
4. Click on ">>" in the pagination toolbar located on the bottom to reach the table last page
5. Observe the total number of clusters keeping to increase in the pagination bars
6. Observe the number of clusters shown in the table page

Actual results:

The number of clusters at step 6 is less than the selected (or default) page size and doen't change during the time.

pagination_bug.webm

Expected results:

The number of clusters at step 6 should reach fast the number equals to the page size.