Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Openstack silently ignores unknown config file entries?

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.