lock_path config option seems to have no effect
Bug #1347915 reported by
Alex Meade
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Valeriy Ponomaryov |
Bug Description
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.
Changed in manila: | |
assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
status: | New → In Progress |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | none → juno-3 |
To post a comment you must log in.
This seems to be an issue with the current manila/ openstack/ common/ lockutils. py which means this may affect other openstack projects as well.