From 8a3e5b4386897a254f70891c06deec254828e3cb Mon Sep 17 00:00:00 2001
From: Mark McLoughlin <markmc@redhat.com>
Date: Sun, 18 Sep 2011 12:04:46 +0100
Subject: [PATCH] Remove VolumeDriver.sync_exec method (lp:819997)

We always use the same functions for sync_exec and execute.

The execute method is always synchronous, so the distinction doesn't
appear to make sense.

Finally, it looks like it would make sense for execute to ever be
async, so the distinction isn't even serving a useful documentation
purpose.

Change-Id: I86d491cfbf8be73672df7cfdf22e465627a86034
---
 nova/tests/test_volume.py | 1 -
 1 file changed, 1 deletion(-)

diff --git a/nova/tests/test_volume.py b/nova/tests/test_volume.py
index 88a73f55..d1b11aaf 100644
--- a/nova/tests/test_volume.py
+++ b/nova/tests/test_volume.py
@@ -271,7 +271,6 @@ class DriverTestCase(test.TestCase):
             """Fake _execute."""
             return self.output, None
         self.volume.driver._execute = _fake_execute
-        self.volume.driver._sync_execute = _fake_execute
 
         log = logging.getLogger()
         self.stream = cStringIO.StringIO()