service_ssl in config never checked for existence or default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Jay Pipes |
Bug Description
Seems like some recent changes to Keystone adding SSL support break older configurations.
After solving bug 897376, I got this:
Starting the Legacy Authentication component
admin : INFO *******
admin : INFO Configuration options gathered from config file:
admin : INFO /tmp/test.
admin : INFO =======
admin : INFO admin_host 0.0.0.0
admin : INFO admin_port 41351
admin : INFO backends keystone.
admin : INFO debug True
admin : INFO default_store sqlite
admin : INFO keystone-admin-role Admin
admin : INFO keystone-
admin : INFO log_file /tmp/test.
admin : INFO service-
'nova' : 'X-Server-
'swift' : 'X-Storage-Url',
'cdn' : 'X-CDN-
admin : INFO service_host 0.0.0.0
admin : INFO service_port 34338
admin : INFO verbose True
admin : INFO *******
Using config file: /tmp/test.
Traceback (most recent call last):
File "/home/
execfile(
File "/home/
if conf['service_ssl'] == 'True':
KeyError: 'service_ssl'
That should instead be a non-erroring check for the service_ssl configuration option.
Cheers,
-jay
Changed in keystone: | |
status: | New → Triaged |
importance: | Undecided → Low |
assignee: | nobody → Jay Pipes (jaypipes) |
Changed in keystone: | |
milestone: | none → essex-2 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | essex-2 → 2012.1 |
Note that pretty much all of the SSL-related variables in bin/keystone suffer from this problem:
certfile, keyfile, ca_certs, certs_required, admin_ssl