Mitaka Cinder SSL issue
Hi All,
I've upgraded to Mitaka from Juno and I've got everything to work correctly using the SSL options except for Cinder.
I've set the options under [ssl] of the cinder.conf file but when the api service starts up it seems to ignore the ssl options and start as http rather than https as the log entry below shows:
eventlet.wsgi.server [-] (43330) wsgi starting up on http ://0.0.0.0:8776/
When I enable debug and restart the service there is no mention of the parameters under the [ssl] section.
Is this a bug with cinder and is there any workaround?
I've been reading some other posts (https://bugs.launchpad.net/puppet-cinder/+bug/1565925 (https://bugs.launchpad.net/puppet-cin...)) and I'm wondering if the ssl options have been removed but I'm not sure how to enable the cinder-api as an apache wsgi process.
So far I have completed the tasks listed here (http://docs.openstack.org/developer/cinder/devref/api.apache.html (http://docs.openstack.org/developer/c...)) but I'm not struggling with the SELinux. I'm getting an the following error:
IOError: [Errno 13] Permission denied: '/var/log/cinder/osapi_volume.log'
Any help would be appreciated.
Thanks,
Simon
Check config reference to see any missed option. http://docs.openstack.org/mitaka/config-reference/block-storage/block-storage-sample-configuration-files.html
I've been through all the configuration options several times and I can't see anything that I have missed.
From the logs it appears when cinder-api is starting up it isn't reading the options from the [ssl] section.
I have the same problem. I've upgraded to Mitaka from Liberty wsgi starting up on http://0.0.0.0:8776/ not https