Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-7062

test-operator should request RWO PVC by default

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • rhos-18.0.0
    • None
    • test-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Hide
      .Tempest test-operator does not work with LVMS storage class

      When the test-operator is used to run Tempest, it requests a “ReadWriteMany” PersistentVolumeClaim (PVC) which the LVMS storage class does not support. This causes the tempest-test pod to become stuck in the `pending` state.

      *Workaround*: Use the test-operator with a storage class supporting `ReadWriteMany` PVCs. The test-operator should work with a  `ReadWriteOnce` PVC so the fixed version will no longer request a `ReadWriteMany` PVC.
      Show
      .Tempest test-operator does not work with LVMS storage class When the test-operator is used to run Tempest, it requests a “ReadWriteMany” PersistentVolumeClaim (PVC) which the LVMS storage class does not support. This causes the tempest-test pod to become stuck in the `pending` state. *Workaround*: Use the test-operator with a storage class supporting `ReadWriteMany` PVCs. The test-operator should work with a  `ReadWriteOnce` PVC so the fixed version will no longer request a `ReadWriteMany` PVC.
    • Release Note Not Required
    • Done
    • Important

      While testing test-operator with the LVMS storage class for OSPRH-2749 the PVC is stuck in pending and then fails.

      openstack                              26s         Warning   ProvisioningFailed          persistentvolumeclaim/tempest-tests-f9c28                               failed to provision volume with StorageClass "lvms-local-storage": rpc error: code = InvalidArgument desc = unsupported access mode: MULTI_NODE_MULTI_WRITER

      LVMS storage class does not support ReadWriteMany access mode. Could this line be removed so that the PVC is requested with ReadWriteOnce instead?

      https://github.com/openstack-k8s-operators/test-operator/blob/839eb81c2b83a54db44a795f3b797413206df4ce/controllers/common.go#L140

      In a follow up patch, if you need to run multiple test-operators for parallel execution maybe you could instead request one PVC per pod.

            lpiwowar Lukáš Piwowarski
            rhn-support-johfulto John Fulton
            rhos-tempest
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: