I would like to update on this week's failures and OST current status.

We had a very eventful week with 2 regressions identified by OST

1. On 11-03-2018 the CI team reported a regression in project ovirt-engine.
The change reported was https://gerrit.ovirt.org/#/c/88738/ - db: add func to turn table columns to empty string. This caused a failure in both master and 4.2 in OST but was also identified to be an issue in 4.1.
The fix for all 3 versions can be tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1554377 and was submitted on 15-03-2018.

I hope that in future we would resolve such regression much faster as it took us 5 days to resolve this issue but I would also like to thank all that helped to resolve it once the issue was investigated more deeply.

2. on 13-03-2018  we found a regression in otopi: core: Use python3 when possible- https://gerrit.ovirt.org/#/c/87276/
The fix was submitted on the same day https://gerrit.ovirt.org/88931 - spec: Package otopi-functions

We also had 1 configuration related issue which was fixed by the CI team and we had failed build-artifacts, mostly in fc27. this was due to the change in fedora to not allow the use of yum and had to be solved by the projects making minor patch changes.

Below you can see the chart for this week's resolved issues but cause of failure:

Code = regression of working components/functionalities
Configurations = package related issues
Other = failed build artifacts
Infra = infrastructure/OST/Lago related issues

Below is a chart of resolved failures based on ovirt version

Below is a chart showing failures by suite type:

Thank you,