Description of problem:

When taking a memory dump with the `virtctl memory-dump` command [1], for example:

===
virtctl memory-dump get -n allowed-live-migrations --storage-class az-b --access-mode=ReadWriteMany --claim-name=memory-dump-2 test-vm-1
===

When looking at the disks of the VM from the UI while the dump PVC is still connected, the disks section crashes with TypeERROR Traceback.

Once the customer runs the `virtctl memory-dump remove` command console works as usual, and reattaching the disk doesn't make it crash again.

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

How reproducible:

Steps to Reproduce:
1. Run $virtctl memory-dump from bastion CLI
2. Open disks section in UI Console
3.

Actual results:
The console crashes and shows a TypeERROR traceback

Expected results:
The console should show actual disk information and should not show Tracebacks.

Additional info:
Doc [1]: https://docs.openshift.com/container-platform/4.12/virt/virt-using-the-cli-tools.html#vm-memory-dump-commands_virt-using-the-cli-tools