Hello,

I would like to update the OST failures and status for the previous week.

before I give the report I would like to say that I have started working on improving our weekly reports and allow better analyses and review of failures so I hope each week the report would become better and more informative.

This week was eventful due to the 4.2 branch being stabilized and also starting to merge some 4.3 related patches to master.

We are still failing on the following tests:

Major issues that were resolved during the week:


I prepared some chart based on this week's alerts and I hope to improve on this in the future.

Please note that i issued the reports based on alerts sent by CQ hence these are not separate issues but alerts sent by the system.

Alerts on resolved issues vs alerts on unresolved issues:

Done = alerts on resolved issues
Backlog = alerts on unresolved issues - these will go to next week's statistics.
Inline image 5

Inline image 6

the below chart is of OST resolved failures based on cause of failure:


Code= regression of working components/functionalities
None= OST did not start to run (this is usually caused by failed artifacts builds)
Infra = packaging and other issues related to our infrastructure
Other = lago/OST related issues
Unknown = anything no falling in those definitions


Inline image 2

Inline image 1



The below is resolved failures based on Suite type:

Basic = Basic Suite
Upgrade - Upgrade from release suite
None = patches that failed because OST did not run (build-artifacts issues)

Inline image 3

Inline image 4


Failures based on Ovirt Version:

Inline image 7

Inline image 8



If you have any requests or suggestions to improve the reporting please let me know.

Thank you,
Dafna