| 2014-07-24 14:48:12 |
Alex Meade |
description |
It seems that manila always tries to create lock files in the current working directory for the manila service and ignores the 'lock_file' configuration option. This is a problem on systems where the manila service does not have permissions to write to the working directory and results in the following issue where the share service cannot start.
See: http://paste.openstack.org/show/87836/ |
It seems that manila always tries to create lock files in the current working directory for the manila service and ignores the 'lock_path' configuration option. This is a problem on systems where the manila service does not have permissions to write to the working directory and results in the following issue where the share service cannot start.
See: http://paste.openstack.org/show/87836/ |
|
