From e16a5f11464b3defb786b45688f5eaeaf2622410 Mon Sep 17 00:00:00 2001
From: Jean-Philippe Evrard <jean-philippe@evrard.me>
Date: Fri, 5 Apr 2019 15:37:14 +0200
Subject: [PATCH] Clarify the worker counts

This is far more complex than what it should be.

Change-Id: Ida97d3ceefa8cd7bb213b1d347d1cce6d0c4af7a
---
 defaults/main.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defaults/main.yml b/defaults/main.yml
index 9a5cb9bd..3f3e6d71 100644
--- a/defaults/main.yml
+++ b/defaults/main.yml
@@ -207,7 +207,7 @@ cinder_swift_catalog_info: "object-store:swift:internalURL"
 
 ## Cap the maximun number of threads / workers when a user value is unspecified.
 cinder_osapi_volume_workers_max: 16
-cinder_osapi_volume_workers: "{{ [[ansible_processor_vcpus|default(2) // 2, 1] | max, cinder_osapi_volume_workers_max] | min }}"
+cinder_osapi_volume_workers: "{{ [ (ansible_processor_vcpus|default(2)) // 2, cinder_osapi_volume_workers_max] | min }}"
 
 ## Cinder iscsi
 cinder_target_helper_mapping: