Description of problem: "ReadOnlyMany" should not added to supported values in memory dump Version-Release number of selected component (if applicable): CNV-v4.12.0-450 Client Version: version.Info{GitVersion:"v0.56.0-rc.0", GitCommit:"7ae67511af8d24e85c1668e6321db08981215e7d", GitTreeState:"clean", BuildDate:"2022-08-01T13:37:38Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"linux/amd64"} How reproducible: Always Steps to Reproduce: 1. Create a VM 2. Do memory dump with an unsupported access mode, got only warning - supported values: "ReadOnlyMany", "ReadWriteMany", "ReadWriteOnce" 3. Do memory dump with access mode "ReadOnlyMany", got warning - cannot dump memory to a readonly pvc Actual results: $ virtctl memory-dump get vm-fedora-datavolume --claim-name=memoryvolume --create-claim --access-mode=RWX PersistentVolumeClaim "memoryvolume" is invalid: spec.accessModes: Unsupported value: "RWX": supported values: "ReadOnlyMany", "ReadWriteMany", "ReadWriteOnce" $ virtctl memory-dump get vm-fedora-datavolume --claim-name=memoryvolume --create-claim --access-mode=ReadOnlyMany cannot dump memory to a readonly pvc, use either ReadWriteOnce or ReadWriteMany if supported Expected results: "ReadOnlyMany" should not added to supported values in memory dump Additional info:
oops, let me correct that, we plan to use the rhel8 versions for 4.12.
Test on CNV-v4.12.0-682, issue has been fixed. $ virtctl memory-dump get vm-fedora-datavolume --claim-name=memoryvolume --create-claim --access-mode=RWX invalid access mode, use either ReadWriteOnce or ReadWriteMany if supported $ virtctl memory-dump get vm-fedora-datavolume --claim-name=memoryvolume --create-claim --access-mode=ReadOnlyMany cannot dump memory to a readonly pvc, use either ReadWriteOnce or ReadWriteMany if supported
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 (Important: OpenShift Virtualization 4.12.0 Images security update), 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/RHSA-2023:0408