Possible race conditions with cinder (nfs) store
Bug #1870289 reported by
Rajat Dhasmana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glance_store |
Fix Released
|
Undecided
|
Unassigned | ||
Train |
Fix Committed
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
With cinder configured as glance store and nfs as cinder backend, there might be a possible race when creating multiple images concurrently during mounting.
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/716874 /git.openstack. org/cgit/ openstack/ glance_ store/commit/ ?id=f5d46996139 593f6249138bcc9 f09b6120f0034a
Committed: https:/
Submitter: Zuul
Branch: master
commit f5d46996139593f 6249138bcc9f09b 6120f0034a
Author: whoami-rajat <email address hidden>
Date: Wed Apr 1 14:18:44 2020 +0000
Add lock per share for cinder nfs mount/umount
With cinder configured as glance store and nfs as cinder backend,
if we create multiple images concurrently into the same share,
there might be race conditions.
This patch ensures a lock per export to avoid the race conditions.
This patch also introduces a reference counting mechamism for unmounting
which will unmount the share if no active thread/process is using it.
Closes-Bug: #1870289
Change-Id: I9197f64e29a0ae 2e0a58186f1a70a a134f7f1db6