Openstack silently ignores unknown config file entries?

asked 2015-03-23 16:10:51 -0600

rlrevell gravatar image

Can anyone explain the reasoning behind this design decision? I believe it would be much easier to troubleshoot config file errors if the daemon in question refuses to start, rather than silently ignoring the error.

In my specific case, I typoed glance_host as glance-host on the block storage node and the result was that cinder create commands worked fine unless the --image-id switch was passed in which case the block storage node tried to connect to glance on its own IP causing volume creations to fail.

edit retag flag offensive close merge delete


Check that the catalog entry for glance i correct

$ keystone catalog as this is where cinder should be getting the endpoint from for glance.

jdexter gravatar imagejdexter ( 2015-03-26 15:47:55 -0600 )edit

The problem was solved by correcting the glance_host in cinder.conf, no changes to any endpoints were required. But it took hours longer than it should have to troubleshoot because invalid config file entries are silently ignored which I think could be considered a bug.

rlrevell gravatar imagerlrevell ( 2015-04-01 16:34:13 -0600 )edit