On my Centos 7 system (CentOS Linux release 7.1.1503), the Cinder processes run under the cinder user.
/var/lock/cinder, used for concurrency, can't be created because the cinder user has no write access to /var/lock (which is a symbolic link to /run/lock).
Possible solutions: Adding write permissions for "other" on /run/lock, or setting up an ACL so that just the cinder user can access the lock directory.
Bernd Bausch noted in the duiplicate bug:
On my Centos 7 system (CentOS Linux release 7.1.1503), the Cinder processes run under the cinder user.
/var/lock/cinder, used for concurrency, can't be created because the cinder user has no write access to /var/lock (which is a symbolic link to /run/lock).
Possible solutions: Adding write permissions for "other" on /run/lock, or setting up an ACL so that just the cinder user can access the lock directory.