← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1788176] Re: placement functional tests can variably fail because of conf

 

Reviewed:  https://review.openstack.org/594172
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b46354d5ab6d59790e69c44bc36a17074155774
Submitter: Zuul
Branch:    master

commit 2b46354d5ab6d59790e69c44bc36a17074155774
Author: Chris Dent <cdent@xxxxxxxxxxxxx>
Date:   Tue Aug 21 14:23:41 2018 +0100

    Set policy_opt defaults in placement gabbi fixture
    
    Without this change, tests can intermittently fail with NoSuchOptError
    when a single process does not have other tests running prior to
    gabbi tests. This change ensure the opts are registered and defaulted.
    
    Change-Id: I1c7e347b6e788928bef96e32c3365d0fdc5ba00f
    Related-Bug: #1786498
    Closes-Bug: #1788176


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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):
  Fix Released
Status in OpenStack Compute (nova) rocky series:
  Confirmed

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


References