Description of problem: Currently in Virtualization -> Overview -> Filesystem usage has a metric about pod filesystem usage, which should be dropped by BZ2072793. Please replace it with actual VM filesystem usage collected by guest agent: # oc rsh virt-launcher-rhel8-accepted-panda-m2ghb sh-4.4# virsh qemu-agent-command 1 '{"execute":"guest-get-fsinfo"}' --pretty { "return": [ { "name": "vda2", "total-bytes": 104634368, "mountpoint": "/boot/efi", "disk": [ { "bus-type": "virtio", "bus": 0, "unit": 0, "pci-controller": { "bus": 4, "slot": 0, "domain": 0, "function": 0 }, "dev": "/dev/vda2", "target": 0 } ], "used-bytes": 6006784, "type": "vfat" }, { "name": "vda3", "total-bytes": 11244908544, "mountpoint": "/", "disk": [ { "bus-type": "virtio", "bus": 0, "unit": 0, "pci-controller": { "bus": 4, "slot": 0, "domain": 0, "function": 0 }, "dev": "/dev/vda3", "target": 0 } ], "used-bytes": 4077879296, "type": "xfs" } ] }
Joao, please assess if adding this metric can be done within 4.11 timeframe. Then we'll ask Shirly/Assaf to make necessary dashboard changes.
the PR is still not merged, moving back to post
Targetting to 4.11.1 as kubevirt relase for 4.11 is already closed.
Ohad, please work with João to verify this bug.
Tested with CNV-4.11.1-20 and the metrics - kubevirt_vmi_filesystem_* is not yet available for consumption. Moving this bug to ASSIGNED state. @Joao, I request you to confirm the non-availability of the fix in 4.11.1 and take the required actions on this bug ( either move the target_release to 4.12 or cherry-pick the fix to 4.11 )
I can cherry-pick, but will only be available for 4.11.2, what do you think @sasundar, @kmajcher ?
(In reply to João Vilaça from comment #7) > I can cherry-pick, but will only be available for 4.11.2, what do you think > @sasundar, @kmajcher ? As this metric provide valuable information about VM filesystem usage, it is good to include that as part of 4.11.z. I agree to include this fix in 4.11.2, but I would still wait for comments from Krzysztof.
Please address in 4.11.2, I've update the target release field accordingly.
verified v4.11.2 kubevirt_vmi_filesystem_* metrics are displayed in 4.11.2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Virtualization 4.11.2 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:0155