| 2015-12-07 08:16:49 |
Ramana Raja |
description |
The glusterfs_native CI is failing. The manila-share service log reports the following error repeatedly,
ERROR manila.share.drivers.glusterfs_native [req-d5d2a89c-27aa-4177-9218-d94b729723fe ] Option auth.ssl-allow is not defined on gluster volume. Volume: manila-glusterfs-native-vol-20G-11
ERROR manila.share.manager [req-d5d2a89c-27aa-4177-9218-d94b729723fe ] Share instance 37c1e2b9-34f5-4702-9dc9-5ca55b97174d failed on creation.
The auth.ssl-allow option needs to be set for a GlusterFS volume to be used as a share. This configuration step does not happen. Looking at the devstacklog (setup log) figured that even though a number of GlusterFS volumes are created to be served as shares, only one of them gets configured properly with auth.ssl-allow option set correctly. |
The glusterfs_native CI is failing. The manila-share service log reports the following error repeatedly,
ERROR manila.share.drivers.glusterfs_native [req-d5d2a89c-27aa-4177-9218-d94b729723fe ] Option auth.ssl-allow is not defined on gluster volume. Volume: manila-glusterfs-native-vol-20G-11
ERROR manila.share.manager [req-d5d2a89c-27aa-4177-9218-d94b729723fe ] Share instance 37c1e2b9-34f5-4702-9dc9-5ca55b97174d failed on creation.
The auth.ssl-allow option needs to be set for a GlusterFS volume to be used as a share. Looking at the devstacklog (setup log), figured that this configuration step does not happen for every volume that is created and is to
be used as a share. |
|
