<div dir="ltr"><div><div><div><div><div><div>Hello, <br><br></div>I would like to update on this week's failure and OST current status. <br><br></div>At the end of the week I am happy to say that we are no longer failing on any issues and the testers are completely green. <br><br></div>We had a great week of many people rallying together to fix OST and resolve all outstanding issues. <br><br></div><div>During the week we saw and resolved the following failures: <br><br></div><b>Master: </b><br><br>002_bootstrap.get_host_devices - this was related to timing issues with the test and was fixed by: <br>
<a href="https://gerrit.ovirt.org/87526" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/87526</a><br><br>001_initialize_engine.initialize_engine - dwh service failed to start - this seemed liked a packaging issue and was resolved. <br><br><br><b>4.2:</b><br><br>002_bootstrap.add_cluster - cluster.cpu.type error - this was resolved a week ago and was resolved by patch: <a href="https://gerrit.ovirt.org/#/c/87126/" target="_blank" title="https://gerrit.ovirt.org/#/c/87126/" rel="noreferrer noopener" class="gmail-josSif" style="color:rgb(0,101,255);text-decoration:underline;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen,Ubuntu,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing:0px;background-color:rgb(255,255,255)">https://gerrit.ovirt.org/#/c/87126/ </a><br><br>003_00_metrics_bootstrap.metrics_and_log_collector - was resolved by Shirly. <br><br>002_bootstrap.get_host_devices - this was related to timing issues with the test and was fixed by: <br>
<a href="https://gerrit.ovirt.org/87526" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/87526</a><br><br><b>4.1</b><br><br>001_initialize_engine.initialize_engine - dwh service failed to start - this seemed liked a packaging issue and was resolved. <br><br></div><div>Build-artifacts jobs failing has a high percentage but<b> many of the build-artifacts failures were caused because of fcraw issues </b>and I am hoping this would be resolved over time. <br><br></div><b>below you can see the chart of OST resolved issues based on cause and failures: </b><br><br></div>* Based on feedback, I made some changes to the definitions<br><br><br>Code= regression of working components/functionalities<br>Configurations - package related issues <br>Other = failed build artifacts<br>Infra = infrastructure/OST/Lago related issues<br><br><br><br><div style="text-align:center"><img src="cid:ii_1619fefbf1cb9906" alt="Inline image 2" width="249" height="203"><br></div><br><div style="text-align:center"><img src="cid:ii_1619fef7082c1a60" alt="Inline image 1" width="534" height="371"><br></div><b>Below is a chart of resolved failures based on Ovirt Version: </b><br><br><br><br><div style="text-align:center"><img src="cid:ii_1619ff6cd76d43a4" alt="Inline image 4" width="221" height="180"><br></div><br><br><div style="text-align:center"><img src="cid:ii_1619ff67415dbdb9" alt="Inline image 3" width="534" height="352"><br><br><br><br><div style="text-align:left"><b>Below is a chart showing failures by suite type: </b><br><br></div><div style="text-align:left">* Suite type None means that it was a failure that did not result in a failed test such artifacts related or packaging related. <br></div><div style="text-align:left"><br><br><div style="text-align:center"><br></div><div style="text-align:center"><img src="cid:ii_1619ffb48710a317" alt="Inline image 8" width="173" height="162"><br></div><br><div style="text-align:center"><br></div><img src="cid:ii_1619ff9bebc01e15" alt="Inline image 7" width="534" height="375"><br></div><div style="text-align:left">Thanks, <br></div><div style="text-align:left">Dafna<br></div><br></div></div>