+++ This bug was initially created as a clone of Bug #2182000 +++

Description of problem:
The metrics graphs of VMs are rendered incorrectly, i.e. the axis lines are not displayed, the axis description is truncated

Version-Release number of selected component (if applicable):
4.12

How reproducible:
ALways

Steps to Reproduce:
1. Use Firefox and access cnv2
2. Look at a VM's metrics, compared to the launcher pod's metrics.
3.

Actual results:
Graphs are rendered differently.
VM graphs seem to be broken

Expected results:
VM graphs are rendered as nicely as pod graphs.

Additional info:
The attached screenshot shows the good pod and bad vm graphs.

— Additional comment from Fabian Deutsch on 2023-03-27 16:15:27 CST —

— Additional comment from Hilda Stastna on 2023-03-27 20:44:04 CST —

Hi Fabian,

this seems to me like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2177961
which has been already fixed for 4.13. Can you please, take a look? Or can you check if it is reproducible in 4.13?
Thanks!

— Additional comment from Fabian Deutsch on 2023-03-27 20:51:27 CST —

Hey Hilda,

yes, the truncation seems to be fixed as part of rhbz #2177961, however, the axis issue is still seen in the screenshot of https://github.com/kubevirt-ui/kubevirt-plugin/pull/1156

I odn't have a 4.13 env at hand right now to check this status.

— Additional comment from Hilda Stastna on 2023-03-27 21:24:15 CST —

See also the PR https://github.com/kubevirt-ui/kubevirt-plugin/pull/1180 for the BZ https://bugzilla.redhat.com/show_bug.cgi?id=2147582
It seems to me that all mentioned in this BZ is already fixed in 4.13.
Also dates were added: https://github.com/kubevirt-ui/kubevirt-plugin/pull/1171

Guohua, can you, please, help us and to test in 4.13 and eventually to close this bug if it's a dup? Thanks!

— Additional comment from Guohua Ouyang on 2023-03-28 07:20:35 CST —

Hi Leon,
Could you help test it completely in 4.13?

Thanks

— Additional comment from Guohua Ouyang on 2023-04-04 10:15:17 CST —

Hi Fabian,
Could you please review the screenshot to see if it looks good to you?

Thanks,

— Additional comment from Leon Kladnitsky on 2023-04-09 10:06:40 CST —

(In reply to Guohua Ouyang from comment #5)
> Hi Leon,
> Could you help test it completely in 4.13?
>
> Thanks

Hi
I will add tests to cover this.

— Additional comment from Fabian Deutsch on 2023-04-11 20:15:05 CST —

> Could you please review the screenshot to see if it looks good to you?

It's a different page than where I reported this bug on.
However, the graphs look ... unclean .. the y-axis is missing and no graph at all is shown in the screenshot.

Is it the correct screenshot?

— Additional comment from Guohua Ouyang on 2023-04-12 07:33:40 CST —

Hi Fabian,
Would you please review this page one more time?

Thanks,

— Additional comment from Fabian Deutsch on 2023-04-12 14:57:17 CST —

Hi Guohua,

attachment 1957019 looks better, but it's still inconsistent, is it?
Memory+CPU are missing the Y-Axis.
Storage r/w + iops have an Y-Axis
Network seems (but the screenshot is truncated) to not have an Y-Axis.

But in all cases (compute, storage, network) the axis description is as expected - not truncated.

— Additional comment from Guohua Ouyang on 2023-04-14 11:00:17 CST —

Hilda,
The Y-Axis is still missing on CPU and Memory graph, could you confirm it and fix it?

— Additional comment from Hilda Stastna on 2023-04-14 20:02:20 CST —

Hi Guohua,

seems that Y-Axis is missing for Memory+CPU and Network graphs also in our freshest 4.14 we are working on now.
So probably I'll need to fix it against 4.14.0 Target Release and than to backport the fix to the older version(s).
To backport it, we will need to set the blocker flag, as we are in "blockers only" stage, AFAIK.
Could you please set the correct version and flag for this bug? Thanks in advance!