[openstack-dev] new failures running Barbican functional tests
doug at doughellmann.com
Tue Mar 10 01:58:07 UTC 2015
On Mon, Mar 9, 2015, at 05:39 PM, Steve Heyman wrote:
> We are getting issues running barbican functional tests - seems to have
> started sometime between Thursday last week (3/5) and today (3/9)
> Seems that oslo config giving us DuplicateOptErrors now. Our functional
> tests use oslo config (via tempest) as well as barbican server code.
> Looking into it...seems that oslo_config is 1.9.1 and oslo_log is 1.0.0
> and a system I have working has oslo_config 1.9 and oslo_log at 0.4 (both
> with same barbican code).
We released oslo.log today with an updated setting for the default log
levels for third-party libraries. The new option in the library
conflicts with the old definition of the option in the incubated code,
so if you have some dependencies using oslo.log and some using the
incubated library you'll see this error.
Updating from the incubated version to the library is not complex, but
it's not just a matter of changing a few imports. There are some
migration notes in this review: https://review.openstack.org/#/c/147312/
Let me know if you run into issues or need a hand with a review.
> Also getting "Failure: ArgsAlreadyParsedError (arguments already parsed:
> cannot register CLI option)"which seems to be related.
This is probably an import order issue. After a ConfigOpts object has
been called to parse the command line you cannot register new command
line options. It's possible the problem is actually caused by the same
module conflict, since both log modules register command line options. I
would need a full traceback to know for sure.
> Is this a known issue? Is there a launchpad bug yet?
> OpenStack Development Mailing List (not for usage questions)
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Email had 1 attachment:
> + signature-with-mafia.png
> 19k (image/png)
More information about the OpenStack-dev