Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

11.2-release UI inconsistent / broken behavior for 'Reporting->Memory' elements and graphs.

Description

While running OS: FreeNAS 11.2-release, discovered inconsistent and unexpected behavior of UI when reviewing reports and analytics for @ 'Reporting' -> 'Memory' element, while switching view options from 'grid' to a 'column' mode.

At times graphs are not displayed at all, at other times graphs, more specifically - the with of the graphs are distorted.
When graphs are missing all together, refreshing the page dose not resolve the issue.
To bring graphs back, user has to chose a different element from the drop down menu like 'CPU', wait until CPU graph is loaded, and than chose the 'Memory' element from the drop down menu to access memory graphs once more.

Client accessing the UI of the FreeNAS 11.2-release instance:

OS: Debian 9 (Stretch) + Gnome Desktop
Browser01: Mozilla Firefox Ver: 60.4.0esr (64-bit)
Browser02: Chromium Version 71.0.3578.80
Protocol: HTTP
Issue(s) persist regarding of the brand/version of the browser(s) used.

Please not that the general performance of the new UI in terms of the speed/responsiveness, relative to the legacy UI - sluggish, in some cases depending what parts/elements of the new UI accessed - almost unusable.

Please see scree-shots attached:

D. Myracle

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Dru Lavigne June 7, 2019 at 6:32 PM

Damien: please watch the related ticket for the resolution of this issue.

William Gryzbowski December 21, 2018 at 6:26 PM

Erin, this may be the same problem as #65232, you may merge the tickets if that the case, please.

Duplicate
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Priority

More fields

Katalon Platform

Created December 19, 2018 at 11:31 PM
Updated July 1, 2022 at 4:26 PM
Resolved June 7, 2019 at 6:32 PM