From 1b2ce8b2ef648b9c00dee53b84ca00b2a05ae3e2 Mon Sep 17 00:00:00 2001 From: "Jay S. Bryant" Date: Tue, 13 Jan 2015 16:25:24 -0600 Subject: [PATCH] Use lockutils.set_defaults to set lock_path in test Commit 9dd6d212f0d8fd74c29077a786fb6d770a2a0bba for oslo.concurrency's lockutils appears to have broken our unit tests. Twelve of the the storwize_svc unit tests started failing with the complaint that the required configuration option 'lock_path' was not set. This change updates cinder/test.py to not only set up a temporary lock_path location that will be automatically cleaned up, but to also register that temporary lock_path location using lockutils.set_defaults() to correct the problem. Change-Id: I011888f676ebc170e7285048b7e5a638a5a8c9a9 Closes-bug: 1410485 --- cinder/test.py | 1 + 1 file changed, 1 insertion(+) diff --git a/cinder/test.py b/cinder/test.py index 176baeaee..7fb7d95fb 100644 --- a/cinder/test.py +++ b/cinder/test.py @@ -189,6 +189,7 @@ class TestCase(testtools.TestCase): config_fixture.Config(lockutils.CONF)) self.fixture.config(lock_path=lock_path, group='oslo_concurrency') + lockutils.set_defaults(lock_path) self.override_config('policy_file', os.path.join( os.path.abspath( -- 2.45.2