- Infra - oVirt List Archives

[CQ]: 106757, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106757,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106757/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19676/

1 0

[CQ]: 106797, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106797,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106797/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19671/

1 0

[CQ]: 104222, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 104222,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/104222/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19666/

1 0

[CQ]: 106787, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106787,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106787/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19661/

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2861: ----------------------------------- Assignee: Barak Korren (was: infra) > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: Barak Korren > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2861 at 2/10/20 10:00 AM: --------------------------------------------------------------- I can see now that you don't have the gh-pages branch stored in Gerrit at all. What you need to do is first push the branch to Gerrit with a "normal" push (I assume you have a copy of it from GitHub), and after you've done that you can wort on it with patches just like you would on any other branch in Gerrit. The automated mirror process to GitHub should cause the pages to show up for your merged changes. was (Author: bkorren(a)redhat.com) I can see now that you don't have the gh-pages stored in Gerrit at all. What you need to do is first push the branch to Gerrit with a "normal" push (I assume you have a copy of it from GitHub), and after you've done that you can wort on it with patches just like you would on any other branch in Gerrit. The automated mirror process to GitHub should cause the pages to show up for your merged changes. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2861: ------------------------------------- I can see now that you don't have the gh-pages stored in Gerrit at all. What you need to do is first push the branch to Gerrit with a "normal" push (I assume you have a copy of it from GitHub), and after you've done that you can wort on it with patches just like you would on any other branch in Gerrit. The automated mirror process to GitHub should cause the pages to show up for your merged changes. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[CQ]: 106789,2 (ovirt-vmconsole) failed "ovirt-master" system tests
by oVirt Jenkins 10 Feb '20

10 Feb '20

Change 106789,2 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106789/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19656/

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Ori Liel (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Ori Liel commented on OVIRT-2861: --------------------------------- Just to be clear, I’ve pushed and merged patches to ovirt-engine-sdk freely using gerrit, the problem only happens to me with this branch, gh-pages. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Ori Liel (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Ori Liel commented on OVIRT-2861: --------------------------------- # git checkout gh-pages (gh-pages is a branch of ovirt-engine-sdk) # commit my changes locally # git push origin HEAD:refs/for/gh-pages Doesn’t work, says it doesn’t recognize the repository. or I’m not authorized. I’ve pushed patches to branches before this way, and it worked. So I asked the previous maintainer of the project what he thinks the problem may be. His answer was: I think you need to push it directly to github, not to gerrit That’s all I know > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[CQ]: 106792, 1 (ovirt-dwh) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106792,1 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 104767,4 (ovirt-dwh) 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 104767,4 (ovirt-dwh) 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/106792/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104767/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19651/

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2861 at 2/10/20 8:04 AM: -------------------------------------------------------------- {quote} I can’t seem to push to it using gerrit {quote} Can you elaborate what you mean by that? do you have the branch configured on the Gerrit side? Merging directly in GitHub will definitely break things, enabling will probably be a bad idea. was (Author: bkorren(a)redhat.com) {quote} seem to push to it using gerrit {quote} Can you elaborate what you mean by that? do you have the branch configured on the Gerrit side? Merging directly in GitHub will definitely break things, enabling will probably be a bad idea. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2861 at 2/10/20 8:03 AM: -------------------------------------------------------------- {quote} seem to push to it using gerrit {quote} Can you elaborate what you mean by that? do you have the branch configured on the Gerrit side? Merging directly in GitHub will definitely break things, enabling will probably be a bad idea. was (Author: bkorren(a)redhat.com) {quote} seem to push to it using gerrit {quote} Can you elaborate what you mean by that, do you have the branch configured on the Gerrit side? Merging directly in GitHub will definitely break things, enabling will probably be a bad idea. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2861: ------------------------------------- {quote} seem to push to it using gerrit {quote} Can you elaborate what you mean by that, do you have the branch configured on the Gerrit side? Merging directly in GitHub will definitely break things, enabling will probably be a bad idea. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Ori Liel (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Ori Liel commented on OVIRT-2861: --------------------------------- Any progress? Changed priority to high > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Ori Liel (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Ori Liel updated OVIRT-2861: ---------------------------- Priority: High (was: Medium) > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[CQ]: 106318, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106318,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106318/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19646/

1 0

[CQ]: 106781, 1 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106781,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106781/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19641/

1 0

[CQ]: 106734, 3 (ovirt-dwh) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106734,3 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 104767,4 (ovirt-dwh) 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 104767,4 (ovirt-dwh) 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/106734/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104767/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19636/

1 0

[CQ]: 106398, 7 (ovirt-dwh) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106398,7 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 104767,4 (ovirt-dwh) 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 104767,4 (ovirt-dwh) 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/106398/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104767/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19631/

1 0

[CQ]: 106675, 5 (ovirt-dwh) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106675,5 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 104767,4 (ovirt-dwh) 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 104767,4 (ovirt-dwh) 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/106675/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104767/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19626/

1 0

oVirt infra daily report - unstable production jobs - 1096
by jenkins＠jenkins.phx.ovirt.org 10 Feb '20

10 Feb '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1096//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 106759, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106759,3 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106384,1 (ovirt-system-tests) 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 106384,1 (ovirt-system-tests) 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/106759/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106384/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19621/

1 0

[CQ]: 106778, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106778,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 106474,1 (ovirt-hosted-engine-setup) 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 106474,1 (ovirt-hosted-engine- setup) 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/106778/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106474/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19616/

1 0

[CQ]: 106610, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106610,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106610/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19610/

1 0

[CQ]: 106780, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106780,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106384,1 (ovirt-system-tests) 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 106384,1 (ovirt-system-tests) 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/106780/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106384/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19604/

1 0

[CQ]: 106772, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106772,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106772/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19598/

1 0

[CQ]: 106545, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106545,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106545/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19592/

1 0

[CQ]: 106773, 1 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106773,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106773/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19586/

1 0

[CQ]: 106423, 9 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106423,9 (ovirt-engine-ui-extensions) failed. However, this change seems not to be the root cause for this failure. Change 105706,7 (ovirt-engine-ui- extensions) 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 105706,7 (ovirt-engine-ui- extensions) 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/106423/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/105706/7 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19580/

1 0

[CQ]: 106761, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106761,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106761/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19574/

1 0

[CQ]: 106764, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106764,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106384,1 (ovirt-system-tests) 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 106384,1 (ovirt-system-tests) 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/106764/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106384/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19568/

1 0

[oVirt Jenkins] cleanup-gated-ovirt-master - Build #56 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Feb '20

09 Feb '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-master/56/ Build Name: #56 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[oVirt Jenkins] cleanup-gated-dummy-master - Build #50 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Feb '20

09 Feb '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/50/ Build Name: #50 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[CQ]: 106731, 9 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106731,9 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106384,1 (ovirt-system-tests) 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 106384,1 (ovirt-system-tests) 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/106731/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106384/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19562/

1 0

[CQ]: 106760, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Feb '20

09 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106760,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106760/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19556/

1 0

oVirt infra daily report - unstable production jobs - 1095
by jenkins＠jenkins.phx.ovirt.org 09 Feb '20

09 Feb '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1095//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 106633, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106633,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106633/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19550/

1 0

[CQ]: 4681206 (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 4681206 (ovirt-ansible-disaster-recovery) failed. However, this change seems not to be the root cause for this failure. Change 88eb306 (ovirt-ansible- disaster-recovery) 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 88eb306 (ovirt-ansible- disaster-recovery) 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://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/4681206eac7… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/88eb3068759… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19544/

1 0

[CQ]: 106756, 1 (ovirt-release) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106756,1 (ovirt-release) failed. However, this change seems not to be the root cause for this failure. Change 106576,1 (ovirt-release) 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 106576,1 (ovirt-release) 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/106756/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106576/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19538/

1 0

[CQ]: 106176, 27 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106176,27 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106176/27 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19532/

1 0

[CQ]: 6654299 (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 6654299 (ovirt-ansible-disaster-recovery) failed. However, this change seems not to be the root cause for this failure. Change 88eb306 (ovirt-ansible- disaster-recovery) 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 88eb306 (ovirt-ansible- disaster-recovery) 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://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/6654299437d… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/88eb3068759… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19526/

1 0

[CQ]: 106709, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106709,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106709/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19520/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #324
by jenkins＠jenkins.phx.ovirt.org 08 Feb '20

08 Feb '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x8…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x8…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision b835bd3bd1811c4748e3b78a0391cb2c900a96b9 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b835bd3bd1811c4748e3b78a0391cb2c900a96b9 Commit message: "ovirt-engine-api-explorer: drop stdci V1 jobs" > git rev-list --no-walk b835bd3bd1811c4748e3b78a0391cb2c900a96b9 # timeout=10 [system-sync_mirrors-centos-updates-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6074062235598643208.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-updates-7.6-el7 yum + local repo_name=centos-updates-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-updates-7.6-el7 /var/www/html/repos/yum/centos-updates-7.6-el7/base + check_yum_sync_needed centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-updates-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-updates-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-updates-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-updates-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-updates-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-7.6-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 106751, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106751,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (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 104391,14 (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/106751/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19514/

1 0

[CQ]: 104275, 23 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 104275,23 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/104275/23 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19508/

1 0

[CQ]: 103721, 3 (cockpit-ovirt) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 103721,3 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 106453,4 (cockpit-ovirt) 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 106453,4 (cockpit-ovirt) 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/103721/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106453/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19502/

1 0

[CQ]: 106267, 9 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106267,9 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106267/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19496/

1 0

[CQ]: 106107, 21 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106107,21 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106107/21 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19490/

1 0

[CQ]: 106748, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '20

08 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106748,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106748/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19484/

1 0