[openstack-dev] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?

Eric K ekcs.openstack at gmail.com
Fri Jan 5 23:16:32 UTC 2018


Seems that sometime between 1/2 and 1/3 this year,
tempest.config.CONF.service_available.aodh_plugin as well as
..service_available.mistral became unavailable in congress dsvm check/gate
job. [1][2]

I've checked the changes that went in to congress, tempest, devstack,
devstack-gate, aodh, and mistral during that period but don't see obvious
causes. Any suggestions on where to look next to fix the issue? Thanks
very much!

Eric Kao

[1] test results from Jan 2; note that aodh is available:
http://logs.openstack.org/54/530154/5/check/congress-devstack-api-mysql/6f8
2f93/logs/testr_results.html.gz
[2] test results from Jan 3; note that aodh is skipped by this line [3],
but aodh is in fact available as seen from the aodh logs [4]:
http://logs.openstack.org/13/526813/11/gate/congress-devstack-api-mysql/7bf
b025/logs/testr_results.html.gz
[3] 
http://git.openstack.org/cgit/openstack/congress/tree/congress_tempest_test
s/tests/scenario/congress_datasources/test_aodh.py#n32
[4] 
http://logs.openstack.org/13/526813/11/gate/congress-devstack-api-mysql/7bf
b025/logs/





More information about the OpenStack-dev mailing list