Logging error after refresh from Oslo Logging repo

[Chad Lung]

A recent update of the Oslo Common code, in particular log.py is causing an issue when you run Barbican in both DevStack and standalone.

Ultimate the error boils down to:
oslo.config.cfg.NoSuchOptError: no such option: log_config

This is because of a naming change done to log.py back on Oct. 2013:
https://github.com/openstack/oslo-incubator/commit/5fef5a8105a85dd8ac07153c48f991fee9726260

When you attempt to start Barbican using the standard uWSGI command as noted in the wiki you will get the error.

[Doug Hellmann (doug-hellmann)]

I wonder why import_opt wasn't throwing an error?

[Chad Lung (chad-lung)]

Hi Doug,

I didn't put the whole stack trace in, but I did capture the import_opt error I believe you are referring to.

More of the stack trace:

 from barbican.common import config

  File "/opt/stack/barbican/barbican/common/config.py", line 35, in <module>

    CONF.import_opt('log_config', 'barbican.openstack.common.log')

  File "/opt/stack/oslo.config/oslo/config/cfg.py", line 1765, in import_opt

    APP, pipeline[-1], global_conf)

  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 458, in

[John Vrbanac (john.vrbanac)]

The devstack gate is no longer failing as a result of this change. This is evident in the following log: http://logs.openstack.org/57/78057/1/check/gate-barbican-devstack-dsvm/92409cb/console.html

Resolving bug...