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

BZ#1638918 Allow volumes to be forcefully unmanaged

XMLWordPrintable

    • Allow volumes to be forcefully unmanaged
    • False
    • False
    • Not Set
    • Committed
    • Committed
    • 100% To Do, 0% In Progress, 0% Done

      Description of problem:
      When the cinder backend is removed, it is not anymore possible to remove the cinder volumes. The volumes remain in deleting state forever.

      Even running openstack volume delete --force –

      There are workarounds to fix this in the DB, but they come with the risk that they become outdated when OpenStack is changing (e.g. https://access.redhat.com/solutions/2578061) they might have undocumented side effects.

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

      How reproducible:
      Each time you remove the cinder backend (in this case ceph).

      Steps to Reproduce:
      1. Add a cinder backend (e.g. ceph)
      2. Stop the backend or removed it form network)
      3. Try to delete any volume that was stored on the cinder backend

      Actual results:
      The volume remains in deleting state.

      Expected results:
      The volume to be deleted

      Additional info:

            eharney@redhat.com Eric Harney
            jira-bugzilla-migration RH Bugzilla Integration
            Yosi Ben Shimon Yosi Ben Shimon
            rhos-dfg-storage-squad-cinder
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: