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

cinder lock paths are inconsistent

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • cinder-operator
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None

      In my podified-antelope deployment (upstream OSP18), Cinder lock files are appearing in multiple directories for cinder-volume:  /var/lib/cinder, and /var/locks/openstack/cinder.

       

      This is because we have two paths to create lock files inside of Cinder and the configuration works differently between them.

      cinder.coordination.synchronized() uses tooz directly and does not respect cinder.conf [oslo_concurrency] lock_path.

      cinder.utils.synchronized() uses oslo_concurrency lock utils which does use the lock_path option.

       

      This means that some locks (clean_incomplete_backups) are in /var/locks/openstack/cinder and some locks (cinder-<uuid>-delete_volume) are in /var/lib/cinder.

      We should get these lock directories pointing to the same location in our deployment.

              eharney@redhat.com Eric Harney
              eharney@redhat.com Eric Harney
              rhos-dfg-storage-squad-cinder
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: