Description of problem: openstack-nova-api service fails to start when the configuration key 'api_paste_config' is left to its default "api-paste.ini" and the init script is invoked from a directory containing a file with the same name. Version-Release number of selected component (if applicable): openstack-nova-api-2013.2-9.el6ost.noarch How reproducible: Steps to Reproduce: 1. openstack-config --set /etc/nova/nova.conf DEFAULT api_paste_config api-paste.ini 2. cd /etc/nova 3. /etc/init.d/openstack-nova-api start Actual results: API service doesn't start and there is a critical message in the logs 2013-12-09 12:57:32.318 3991 CRITICAL nova [-] Cannot resolve relative uri 'config:api-paste.ini'; no relative_to keyword argument given Expected results: Additional info: When a relative path is specified in the 'api_paste_config' key, if the app loader finds a file named exactly with the same name in the current directory it won't try to get the absolute path for it. On the other hand, paste.deploy expects the path to be absolute if no base directory has been specified (which is the case), failing otherwise. See https://github.com/openstack/nova/blob/master/nova/wsgi.py#L467
verified: # rpm -qa |grep openstack-nova openstack-nova-console-2013.2.2-2.el6ost.noarch openstack-nova-scheduler-2013.2.2-2.el6ost.noarch openstack-nova-common-2013.2.2-2.el6ost.noarch openstack-nova-conductor-2013.2.2-2.el6ost.noarch openstack-nova-novncproxy-2013.2.2-2.el6ost.noarch openstack-nova-cert-2013.2.2-2.el6ost.noarch openstack-nova-api-2013.2.2-2.el6ost.noarch also, ran regression on Horizon as it uses nova-api on its queries
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0231.html