From 13c588373c2bb22f25c742d510173fee7b071e3f Mon Sep 17 00:00:00 2001
From: Masayuki Igawa <masayuki@igawa.io>
Date: Wed, 6 Mar 2019 22:01:37 +0900
Subject: [PATCH] Set concurrency default value

This commit sets the default value 0 for tempest run command.
Because stestr's run_command() requires an int value for that, but we
passes `None` if users don't specify a concurrency value. We found that
behavior with recent stestr change[0]. But we also have the bug in
tempest side.

[0] https://github.com/mtreinish/stestr/issues/231

Change-Id: I83f76acb6a106f7401904a910a5dced47c2db839
---
 tempest/cmd/run.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tempest/cmd/run.py b/tempest/cmd/run.py
index a8ef08c475..823ed118b6 100644
--- a/tempest/cmd/run.py
+++ b/tempest/cmd/run.py
@@ -252,7 +252,7 @@ class TempestRun(command.Command):
                             default=False)
         # execution args
         parser.add_argument('--concurrency', '-w',
-                            type=int,
+                            type=int, default=0,
                             help="The number of workers to use, defaults to "
                                  "the number of cpus")
         parallel = parser.add_mutually_exclusive_group()