Re: OST Failure - Weekly update [03/03/2018-09/03/2018]
On Fri, Mar 9, 2018 at 10:02 PM, Dafna Ronwrote: > Hello, > > I would like to update on this week's failures and OST current status. > > We had a few failure this week: > > 1. A change in OST caused a failure in one of the tests. this was due to > using a 4.3 SDK feature which is not available in the current SDK version. > The change was https://gerrit.ovirt.org/#/c/84338 - > https://gerrit.ovirt.org/#/c/84338/ > We reverted the change: https://gerrit.ovirt.org/#/c/88441/ > I believe that we where able to take this patch due to a bug in OST, which I believe Daniel already works on: the patch modified a file that is linked from the suite-4.2, but the CI job for the patch triggered only suite-master. We should be more prudent, as long as we use cross-suite symlinks. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
OST Failure - Weekly update [03/03/2018-09/03/2018]
Hello, I would like to update on this week's failures and OST current status. We had a few failure this week: 1. A change in OST caused a failure in one of the tests. this was due to using a 4.3 SDK feature which is not available in the current SDK version. The change was https://gerrit.ovirt.org/#/c/84338 - https://gerrit.ovirt.org/#/c/84338/ We reverted the change: https://gerrit.ovirt.org/#/c/88441/ However, this merge actually exposed an issue in the vdsm logs which report guest agent errors. bug was opened: https://bugzilla.redhat.com/show_bug.cgi?id=1553893 2. We discovered that there was a syntax error in 'release_branches' in ovirt-ansible. we re-merged after fixing the issue - Thanks you Barak/Sandro and Ondra for investigating and fixing the issue. This solved issues that were caused by running tests from stable older ansible packages. 3. fcraw build-artifacts jobs were removed since they were causing changes to fail running on cq. it was decided that its better to disable those jobs for now. 4. we have a second failure in build-artifacts for fc27 which caused several changes that were merged in cockpit-ovirt to fail. Thank you Douglas for acting quickly to resolve the issue. *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, Dafna ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra