From 37b7a2097a5a8ba1223ba180fcf30f86b188b20e Mon Sep 17 00:00:00 2001
From: Patrick East <patrick.east@purestorage.com>
Date: Thu, 11 Aug 2016 20:46:14 -0700
Subject: [PATCH] Add release note to warn about os-brick lock dir

Not really a new bug, but turns out this wasn't generally known
or documented anywhere. As a heads up for folks we'll put in a
known issue into the release note for N.

Change-Id: Ied267c84dee2473e592eb737baab630954a2b5b3
---
 .../notes/os-brick-lock-dir-35bdd8ec0c0ef46d.yaml        | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 releasenotes/notes/os-brick-lock-dir-35bdd8ec0c0ef46d.yaml

diff --git a/releasenotes/notes/os-brick-lock-dir-35bdd8ec0c0ef46d.yaml b/releasenotes/notes/os-brick-lock-dir-35bdd8ec0c0ef46d.yaml
new file mode 100644
index 00000000000..a4fbf456d3f
--- /dev/null
+++ b/releasenotes/notes/os-brick-lock-dir-35bdd8ec0c0ef46d.yaml
@@ -0,0 +1,9 @@
+---
+issues:
+  - When running Nova Compute and Cinder Volume or Backup services on the same
+    host they must use a shared lock directory to avoid rare race conditions
+    that can cause volume operation failures (primarily attach/detach of
+    volumes). This is done by setting the "lock_path" to the same directory
+    in the "oslo_concurrency" section of nova.conf and cinder.conf. This issue
+    affects all previous releases utilizing os-brick and shared operations
+    on hosts between Nova Compute and Cinder data services.
\ No newline at end of file