Comment 2 for bug 1347915

1) There is no such option as 'lock_file' in configuration.
2) There are option 'lock_path', that has default value to env var 'MANILA_LOCK_PATH', see:
https://github.com/stackforge/manila/blob/2a0890e3580f0cf1e7578c1f59eef55431ef0c65/manila/openstack/common/lockutils.py#L43

So, this can be changed in 2 (two) ways:

- set env var 'MANILA_LOCK_PATH' to some value, for example:
export MANILA_LOCK_PATH=/tmp/
It will use this dir as lock storage.

- set 'lock_path' opt in Manila's configuration.

In conclusion: there is no bug in Manila code, there is wrong configuration.