yahoo-eng-team team mailing list archive

[Jerome Pansanel <j.pansanel@xxxxxxxxxxxx>]

Public bug reported:

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>
sys.exit(main())
File "/usr/lib/python2.7/site-packages/nova/cmd/api.py", line 44, in main
if 'osapi_compute' in CONF.enabled_apis:
File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2485, in __getattr__
return self._get(name)
File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2929, in _get
value = self._do_get(name, group, namespace)
File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2972, in _do_get
% (opt.name, 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:
enabled_apis=osapi_compute,metadata,ooi
 
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 (https://github.com/openstack/ooi).

After some investigation, I have seen that the issue is a consequence from this commit:
https://github.com/openstack/nova/commit/e8436283e45b6716fb61d6f6590fadb5fb4ba45c#diff-d4b6199156ad8829f4d47d89d9eef4a7

The bug is fixed when I remove lines 84 ad 85 in
https://github.com/openstack/nova/blob/master/nova/conf/service.py.

Is there any reason to enforce the value of enabled_apis?

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1751036

Title:
  ConfigFileValueError when defining enabled_apis

Status in OpenStack Compute (nova):
  New

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>
  sys.exit(main())
  File "/usr/lib/python2.7/site-packages/nova/cmd/api.py", line 44, in main
  if 'osapi_compute' in CONF.enabled_apis:
  File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2485, in __getattr__
  return self._get(name)
  File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2929, in _get
  value = self._do_get(name, group, namespace)
  File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2972, in _do_get
  % (opt.name, 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:
  enabled_apis=osapi_compute,metadata,ooi
   
  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 (https://github.com/openstack/ooi).

  After some investigation, I have seen that the issue is a consequence from this commit:
  https://github.com/openstack/nova/commit/e8436283e45b6716fb61d6f6590fadb5fb4ba45c#diff-d4b6199156ad8829f4d47d89d9eef4a7

  The bug is fixed when I remove lines 84 ad 85 in
  https://github.com/openstack/nova/blob/master/nova/conf/service.py.

  Is there any reason to enforce the value of enabled_apis?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1751036/+subscriptions