yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74372
[Bug 1788176] [NEW] placement functional tests can variably fail because of conf
Public bug reported:
When running just the placement functional tests with `tox -efunctional
placement` on a host with sufficient cpus (16 in this case, on a host
with only 4 it wasn't happening) some tests can fail because of conf not
being properly set with "oslo_config.cfg.NoSuchOptError: no such option
oslo_policy in group [DEFAULT]". Example traceback at
http://paste.openstack.org/show/728513/
This appears to because in some cases registering the policy opts is
happening elsewhere in the processing before running the gabbi tests but
only sometimes. This is a symptom of long term global conf leakage that
we may wish to consider fixing, but the short term fix is to register
the opts in the gabbi fixture. Patch forthcoming.
** Affects: nova
Importance: Medium
Assignee: Chris Dent (cdent)
Status: In Progress
** Tags: placement testing
--
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/1788176
Title:
placement functional tests can variably fail because of conf
Status in OpenStack Compute (nova):
In Progress
Bug description:
When running just the placement functional tests with `tox
-efunctional placement` on a host with sufficient cpus (16 in this
case, on a host with only 4 it wasn't happening) some tests can fail
because of conf not being properly set with
"oslo_config.cfg.NoSuchOptError: no such option oslo_policy in group
[DEFAULT]". Example traceback at
http://paste.openstack.org/show/728513/
This appears to because in some cases registering the policy opts is
happening elsewhere in the processing before running the gabbi tests
but only sometimes. This is a symptom of long term global conf leakage
that we may wish to consider fixing, but the short term fix is to
register the opts in the gabbi fixture. Patch forthcoming.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1788176/+subscriptions
Follow ups