Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-21015

[2124147] "ReadOnlyMany" should not be added to supported values in memory dump

XMLWordPrintable

    • Storage Core Sprint 225, Storage Core Sprint 226, Storage Core Sprint 227
    • Medium

      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:

            skagan@redhat.com Shelly Kagan
            yadu1@redhat.com Yan Du
            Yan Du Yan Du
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: