Activity log for bug #1818560

Date Who What changed Old value New value Message
2019-03-04 18:53:19 Chris Dent bug added bug
2019-03-04 20:14:15 OpenStack Infra nova: status Confirmed In Progress
2019-03-04 20:14:15 OpenStack Infra nova: assignee Chris Dent (cdent)
2019-03-04 20:21:58 Chris Dent summary Nova's use of the placement database fixture from test_report_client doesn't register opts Nova test_report_client uses nova conf when starting placement intercept, causing missing config opts
2019-03-04 20:23:13 Chris Dent description See: http://logs.openstack.org/98/538498/22/gate/nova-tox-functional-py35/7673d3e/testr_results.html.gz The failing tests there are failing because the Database fixture from placement is used directly, and configuration opts are not being registered properly. This was an oversight when adding a new configuration setting. The fix is to register the missing opt when requested to do so. This is blocking the gate. See: http://logs.openstack.org/98/538498/22/gate/nova-tox-functional-py35/7673d3e/testr_results.html.gz The failing tests there are failing because the Database fixture from placement is used directly, and configuration opts are not being registered properly. This was an oversight when adding a new configuration setting. The fix is to register the missing opt when requested to do so. This is blocking the gate. LATER, to clarify: The root cause of this is that in test_report_client, a global CONF from nova was being used to create the placement wsgi-intercepts. When a new config was added on the placement side, that global CONF was no longer in sync.
2019-03-04 22:31:49 OpenStack Infra nova: assignee Chris Dent (cdent) Eric Fried (efried)
2019-03-05 02:27:21 OpenStack Infra nova: status In Progress Fix Released
2019-03-11 15:24:29 Matt Riedemann nova: assignee Eric Fried (efried) Chris Dent (cdent)