-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
False
-
None
Description of problem:
A cluster with a lot of cluster history records and cluster history record count per page is set for example, 20 per page.
User has navigated from the first to last page of loaded history and then makes changes to the cluster history record count per page to higher than current value i.e. either 50 per page or 100 per page.
As a result of this action, the Cluster history tab itself vanishes from the OCM pane. User needs to reopen the cluster page in OCM to view the cluster history tab again.
How reproducible:
Always
Steps to Reproduce:
- Launch OCM staging env.
- Go to a cluster that has a lot of cluster history records(approx 30 rows).
- Set the records count per page , say as 20 per page.
- Navigate from the first page to last page of the cluster history with the help of > icon.
- Change the cluster history display count > 20 (for ex: 20 per page to 100 per page).
- View the behavior.
Actual results:
Cluster history tab vanishes from UI when user changes the display count greater than current value after reaching the last page of history list.
Browser console logs
src_js_bootstrap_js-src_js_unfetch_index_js-node_modules_redhat-cloud-services_frontend-compo-4f5f41.dae0523b22d7b05cb7eb.js:6765 GET https://api.stage.openshift.com/api/service_logs/v1/clusters/e7953ed3-3007-488e-95d6-8a65611651ae/cluster_logs?size=100&page=2&orderBy=timestamp+desc&search=(timestamp+%3E%3D+%272022-09-05T00:00:00.000Z%27) 500
sendReplacement @ src_js_bootstrap_js-src_js_unfetch_index_js-node_modules_redhat-cloud-services_frontend-compo-4f5f41.dae0523b22d7b05cb7eb.js:6765
(anonymous) @ trycatch.js:188
(anonymous) @ instrument.js:239
(anonymous) @ xhr.js:178
e.exports @ xhr.js:12
e.exports @ dispatchRequest.js:50
Promise.then (async)
u.request @ Axios.js:61
(anonymous) @ bind.js:9
getClusterHistory @ serviceLogService.js:3
(anonymous) @ clusterLogActions.js:7
(anonymous) @ index.js:8
(anonymous) @ middleware.js:26
boundActionCreators.<computed> @ vendors-node_modules_react-redux_es_index_js.dae0523b22d7b05cb7eb.js:1556
value @ ClusterLogs.jsx:68
value @ ClusterLogs.jsx:63
commitLifeCycles @ chrome-root.dae0523b22d7b05cb7eb.js:23293
commitLayoutEffects @ chrome-root.dae0523b22d7b05cb7eb.js:26035
callCallback @ chrome-root.dae0523b22d7b05cb7eb.js:6559
r @ helpers.js:71
invokeGuardedCallbackDev @ chrome-root.dae0523b22d7b05cb7eb.js:6608
invokeGuardedCallback @ chrome-root.dae0523b22d7b05cb7eb.js:6670
commitRootImpl @ chrome-root.dae0523b22d7b05cb7eb.js:25760
unstable_runWithPriority @ chrome-root.dae0523b22d7b05cb7eb.js:32107
runWithPriority$1 @ chrome-root.dae0523b22d7b05cb7eb.js:13890
commitRoot @ chrome-root.dae0523b22d7b05cb7eb.js:25599
performSyncWorkOnRoot @ chrome-root.dae0523b22d7b05cb7eb.js:24938
(anonymous) @ chrome-root.dae0523b22d7b05cb7eb.js:13941
unstable_runWithPriority @ chrome-root.dae0523b22d7b05cb7eb.js:32107
runWithPriority$1 @ chrome-root.dae0523b22d7b05cb7eb.js:13890
flushSyncCallbackQueueImpl @ chrome-root.dae0523b22d7b05cb7eb.js:13936
flushSyncCallbackQueue @ chrome-root.dae0523b22d7b05cb7eb.js:13923
discreteUpdates$1 @ chrome-root.dae0523b22d7b05cb7eb.js:25029
discreteUpdates @ chrome-root.dae0523b22d7b05cb7eb.js:6370
dispatchDiscreteEvent @ chrome-root.dae0523b22d7b05cb7eb.js:8503
createError.js:16 Uncaught (in promise) Error: Request failed with status code 500
at e.exports (createError.js:16:15)
at e.exports (settle.js:17:12)
at l.onreadystatechange (xhr.js:61:7)
at XMLHttpRequest.r (helpers.js:71:23)
Expected results:
Cluster history tab should display the records as per the user selection i.e. in this case ,100 records should be loaded in each page of cluster history tab.
Additional info:
Please find the attached screenshare.
- is related to
-
HAC-146 OCM UI: shift cluster history to its own tab
-
- Closed
-
- mentioned on
