-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
0.5
-
False
-
-
False
-
-
-
ACM Console Sprint 250
-
Critical
Description of the issue
Under cluster history tab of any installed cluster, it was seen that the log filter functionality by Severity, Type, logged by etc seems broken and not working. The browser console log report below errors
112 Uncaught TypeError: Cannot destructure property 'severityTypes' of 'C.current' as it is undefined. at I (ClusterLogsConditionalFilter.jsx:67:13) at r (helpers.js:90:17)
See the recordings ClusterHistoryBrokenLogFilter.mp4ClusterHistoryBrokenLogFilter.mp4{}**{}
Steps to Reproduce:
- Launch OCM UI staging.
- Open ready cluster and go to a cluster history tab.
- Filter the logs by severity, Type, logged by options.
- See the behavior.
Actual results:
The log filter functionality is broken and not filtered the log record as expected.
Expected results:
All the supported log filter functionalities should work without any issue for any cluster in OCM UI.
- depends on
-
OCMUI-1326 OCMUI-1326: ClusterDetailsSubscriptionId component tree refactoring and updating to use v6 api
- Closed