The enabled_apis in nova are fixed for interoperability reasons. There
is only one nova compute API.

If you want to run another API, then you should do so like the ec2 or
GCE proxies, e.g.:

You can run your own service and add your own entry to the service
catalog, but it's not nova.

** Changed in: nova
       Status: New => Won't Fix

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  ConfigFileValueError when defining enabled_apis

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  After the upgrade of our OpenStack Cloud infrastructure from Newton to Pike, 
the following error has appeared:
  Traceback (most recent call last):
  File "/usr/bin/nova-api", line 10, in <module>
  File "/usr/lib/python2.7/site-packages/nova/cmd/", line 44, in main
  if 'osapi_compute' in CONF.enabled_apis:
  File "/usr/lib/python2.7/site-packages/oslo_config/", line 2485, in 
  return self._get(name)
  File "/usr/lib/python2.7/site-packages/oslo_config/", line 2929, in _get
  value = self._do_get(name, group, namespace)
  File "/usr/lib/python2.7/site-packages/oslo_config/", line 2972, in 
  % (, str(ve)))
  ConfigFileValueError: Value for option enabled_apis is not valid: Valid 
values are [osapi_compute, metadata], but found 'ooi,ec2'

  It comes from the fact that we are defining the enabled_apis parameter in 
nova.conf like:
  It is for us a requirement to be able to define the enabled_apis parameter. 
We are member of the EGI Cloud federation, that requires an additional API to 
be available to the users (OCCI). This API is made available through the OOI 
project (

  After some investigation, I have seen that the issue is a consequence from 
this commit:

  The bug is fixed when I remove lines 84 ad 85 in

  Is there any reason to enforce the value of enabled_apis?

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to