OST Failure - Weekly update [07/04/2018-13/04/2018]

Hello, I would like to update on this week's failures and OST current status. We had some issues from previous week. once is still sporadically failing but since there were a few patches merged and another one in the processes I decided we can close this sprint with no backlog. this week's failures were one regression, sporadic failures and one packaging issue. We are still seeing sporadic failures on migration tests but Gal has a fix which would probably be merged soon. https://gerrit.ovirt.org/#/c/90166/ - master,4.2: Wait for migration to end we have found and reported a regression change: https://gerrit.ovirt.org/#/c/89581/ - Subnet name should be an optional field This was fixed quickly by: https://gerrit.ovirt.org/#/c/89980/ - Fix mistaken mapping for retrieving subnet name from row We moved to Ansible 2.5 but the packages were not updated in the repos. this was fixed by this change: https://gerrit.ovirt.org/#/c/90015/ - 4.2: Take ansible from epel *Below you can see the chart for this week's resolved issues but cause of failure:**Code* = regression of working components/functionalities *Infra* = infrastructure/OST Infrastructure/Lago related issues/Power outages *OST* *Tests *- package related issues, failed build artifacts *Below is a chart of resolved failures based on ovirt version:* *Below is a chart showing failures by suite type: * *Below you can see the issues opened this week vs the backlog issues from previous week: * Thanks, Dafna