- Infra - oVirt List Archives

[CQ]: 88362, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88362,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88362/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6249/

1 0

[CQ]: 88718, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88718,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88738,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88718/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1196/

1 0

[CQ]: 88717, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88717,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88738,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88717/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1195/

1 0

standard CI packages files
by Yedidyah Bar David 12 Mar '18

12 Mar '18

Hi all, The various automation/*.packages* files are rather hard to maintain - with many partial duplicates, symlinks, and changes applied to some file forgotten to be applied to others that needed them. Can we have something more dynamic? E.g. that CI will run a single script, e.g. automation/get-needed-packages, provide it as args the action to be ran ("check-patch", "build-artifacts" etc.) and the distro ("el7", "fc27" etc.) and use whatever it outputs as the list of packages to install? Thanks, -- Didi

2 3

OST testing and releases of ovirt-ansible-* projects
by Barak Korren 12 Mar '18

12 Mar '18

Due to an issue we had with our post-merge triggering code for GitHub, most merge event for Github projects were not handled and therefore theses projects were not processes by the change queue and not released into the nightly repos. We've now resolved the issue and replayed the most recent merge event for the `ovirt-ansible` project. I need to know if there are any other projects on GitHub that need to release RPMs via the oVirt change queue. If so, we probably need to take action to generate merge events for them by either merging new changes or replaying older merge events. Please let me know, Thanks, -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 2

[CQ]: 88772, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88772,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88772/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6247/

1 0

[CQ]: 88670, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88670,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88670/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6246/

1 0

[oVirt Jenkins] ovirt-appliance_4.2_build-artifacts-el7-x86_64 - Build # 7 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Mar '18

12 Mar '18

------=_Part_131_2080624497.1520766910612 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_64… Build Number: 7 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #7 [Barak Korren] Adapt for lowercase GitHub headers [Sandro Bonazzola] build: use 4.2 snapshot release rpm ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_131_2080624497.1520766910612--

1 1

[CQ]: 88760, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88760,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88760/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6244/

1 0

[CQ]: 88646, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88646,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88646/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6242/

1 0