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

Watcher can't migrate volumes with volume type not associated with the 'volume_backend_name' of the destination pool

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-workloads-evolution
    • None
    • Important

      To Reproduce Steps to reproduce the behavior:

      1. Deploy an openstack cluster with multiple cinder backends and each with a different 'volume_backend_name'
      2. Create an audit with the zone migration strategy to migrate a volume from a pool in one backend to a pool in another backend

      Expected behavior

      • The volume is migrated to the destination pool. Instead

      Bug impact

      • Any volume migration in a cluster with the storage setup described will fail.

      Known workaround

      • Configure volume types with a volume_backend_name, and all cinder backends that the user wants to migrate volumes between with the same volume_backend_name

              jgilaber@redhat.com Joan Francesc Gilabert Navarro
              jgilaber@redhat.com Joan Francesc Gilabert Navarro
              rhos-workloads-evolution
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: