7be9c10679dbc7a6426e4f0c17b86750b1d95a3b
Not long ago we enabled a rally scenario booting VMs in the neutron gate so we can collect osprofiler reports about it. The rally scenario we re-used was only triggered by changes in the rally-openstack repo so I could not collect data about its failure rate. Now that it's running frequently in the neutron gate this scenario actually seems to be quite unstable (usually timing out while waiting for the VM to get to ACTIVE): http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:\"rally.exceptions.TimeoutException: Rally tired waiting\" AND build_name:\"neutron-rally-task\" AND voting:1&from=864000s Since we only want to run this scenario for the osprofiler report we can get rid of the gate instability by allowing a 100% failure rate in the scenario SLA. Change-Id: Ied354e8242274c8eeb26909e29afbe6d41662bfc Related-Change: https://review.opendev.org/662804
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst
Description
Languages
Python
99.7%
Shell
0.3%