From 65978582e01c37a9972bf9e979c651523f0f1889 Mon Sep 17 00:00:00 2001 From: Patrick East Date: Thu, 11 Aug 2016 20:46:01 -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: Icc06da4399446b6d537aac9ee4d00df8226580c4 --- .../notes/os-brick-lock-dir-c659089679aac50f.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/os-brick-lock-dir-c659089679aac50f.yaml diff --git a/releasenotes/notes/os-brick-lock-dir-c659089679aac50f.yaml b/releasenotes/notes/os-brick-lock-dir-c659089679aac50f.yaml new file mode 100644 index 000000000000..c4968300f8a6 --- /dev/null +++ b/releasenotes/notes/os-brick-lock-dir-c659089679aac50f.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.