I reproduced this using a standalone build based on train. The cinder-volume service is running as the 'cinder' user, but /var/lib/cinder is owned by root and so cinder cannot create the /var/lib/cinder/groups directory.
Note: In train's standalone deployment, cinder-volume is not run under pacemaker. in later releases, even standalone deployment runs c-vol under pacemaker. Under pacemaker, c-vol runs as root, so it has perms to create the /var/lib/cinder/groups directory.
I think the issue is the TCIB framework isn't installing a the extend_start.sh script that kolla images provide. See [1], where the c-vol extend_start.sh sets the ownership of /var/lib/cinder.
I reproduced this using a standalone build based on train. The cinder-volume service is running as the 'cinder' user, but /var/lib/cinder is owned by root and so cinder cannot create the /var/lib/ cinder/ groups directory.
Note: In train's standalone deployment, cinder-volume is not run under pacemaker. in later releases, even standalone deployment runs c-vol under pacemaker. Under pacemaker, c-vol runs as root, so it has perms to create the /var/lib/ cinder/ groups directory.
I think the issue is the TCIB framework isn't installing a the extend_start.sh script that kolla images provide. See [1], where the c-vol extend_start.sh sets the ownership of /var/lib/cinder.
[1] https:/ /opendev. org/openstack/ kolla/src/ branch/ master/ docker/ cinder/ cinder- volume/ extend_ start.sh# L4
I looked for something equivelent in [2], where the TCIB extend_start scripts appear to be located, but I don't see anything for cinder-volume.
[2] https:/ /opendev. org/openstack/ tripleo- common/ src/branch/ stable/ train/container -images/ kolla
This is pretty much the limit of my knowledge of TCIB, but hopefully someone who knows more can make something of this.