- Infra - oVirt List Archives

[vdsm][tag][master] Vdsm tagged: v4.20.15
by Francesco Romani 23 Jan '18

23 Jan '18

Hi infra, Hi infra, we have a new Vdsm tag on branch master for oVirt 4.2: tag v4.20.15 Tagger: Francesco Romani <fromani(a)redhat.com> Date: Tue Jan 23 11:16:41 2018 +0100 Vdsm 4.20.15 for oVirt 4.2.1 RC 4 commit b5b771f2152225b2c262c5ed3148acd53ee5f17b +++ NOTE ABOUT BRANCHING: * We are merging again patches targeted for 4.2.1 on master * We don't yet have plans to branch out ovirt-4.2 from master. Following the usual Vdsm habit, we will branch out late, *after* Engine does. Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

1 0

[oVirt Jenkins] standard-enqueue - Build #9158 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jan '18

23 Jan '18

------=_Part_257_1141798880.1516697727396 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9158/ Build Name: #9158 Build Description: Gerrit: 86664 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/86664 - title: build: ovirt-engine-3.6.13 - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_257_1141798880.1516697727396--

1 1

[CQ]: 85809,14 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 23 Jan '18

23 Jan '18

Change 85809,14 (ovirt-engine) 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/85809/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5047/

1 0

[CQ]: 86662, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86677, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86677, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86671,1 (ovirt-log-collector) failed "ovirt-4.2" system tests
by oVirt Jenkins 23 Jan '18

23 Jan '18

Change 86671,1 (ovirt-log-collector) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/86671/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/321/

1 0

[CQ]: 86662, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86661, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86660, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86659, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '18

23 Jan '18

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

1 0

[CQ]: 86658, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86656, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86655, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86654, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86653, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86652, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86651, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86650, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

[CQ]: 86649, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jan '18

22 Jan '18

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

1 0

Fwd: [oVirt/openshift-status-cachet] One of your dependencies may have a security vulnerability
by Yaniv Kaul 22 Jan '18

22 Jan '18

---------- Forwarded message ---------- From: GitHub <notifications(a)github.com> Date: Mon, Jan 22, 2018 at 5:48 PM Subject: [oVirt/openshift-status-cachet] One of your dependencies may have a security vulnerability To: oVirt/openshift-status-cachet < openshift-status-cachet(a)noreply.github.com> Cc: Security alert <security_alert(a)noreply.github.com> We found a potential security vulnerabilty in one of your dependencies [image: GitHub] <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBlaoUQ7ZnNS…> Sign in <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBluE-2FGrtU…> *mykaul,* We found a potential security vulnerability in a repository which you have been granted security alert access. [image: @oVirt] oVirt/openshift-status-cachet <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBsTdbr6tFZv…> Known * moderate severity* security vulnerability detected in jquery < 3.0.0 defined in package.json <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBsTdbr6tFZv…>. package.json <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBsTdbr6tFZv…> update suggested: jquery ~> 3.0.0. Always verify the validity and compatibility of suggestions with your codebase. Review vulnerable dependency <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBsTdbr6tFZv…> ------------------------------ Only users who have been assigned access to security alerts will receive these notifications. Unsubscribe <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBh4tM-2Bvbn…> · Email preferences <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBlttXBNYv-2…> · Terms <http://sgmail.githubmail.com/wf/click?upn=H-2FQ3yMxnv4jw-2BxNnSBX80-2FAtA3t…> · Privacy <http://sgmail.githubmail.com/wf/click?upn=H-2FQ3yMxnv4jw-2BxNnSBX80-2FAtA3t…> · Sign into GitHub <http://sgmail.githubmail.com/wf/click?upn=lYxq-2FYU7yocrdKNILYalBluE-2FGrtU…> GitHub, Inc. 88 Colin P Kelly Jr St. San Francisco, CA 94107 <https://maps.google.com/?q=88+Colin+P+Kelly+Jr+St.%0D+San+Francisco,+CA+941…>

2 1

[CQ]: 86648,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Jan '18

22 Jan '18

Change 86648,1 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/274/

1 0

[JIRA] (OVIRT-1857) Please create ovirt-ansible-dpdk-setup github repostiory
by Daniel Belenky (oVirt JIRA) 22 Jan '18

22 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1857?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1857: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Please create ovirt-ansible-dpdk-setup github repostiory > -------------------------------------------------------- > > Key: OVIRT-1857 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1857 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: Daniel Belenky > > Please create ovirt-ansible-dpdk-setup github repostiory > And please assign igoihman as administrator. > Thanks. > [~igoihman(a)redhat.com] > [~mwperina] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1857) Please create ovirt-ansible-dpdk-setup github repostiory
by Daniel Belenky (oVirt JIRA) 22 Jan '18

22 Jan '18

This is a multi-part message in MIME format... ------------=_1516632284-28099-266 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1857?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1857: ---------------------------------- Status: In Progress (was: To Do) > Please create ovirt-ansible-dpdk-setup github repostiory > -------------------------------------------------------- > > Key: OVIRT-1857 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1857 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Please create ovirt-ansible-dpdk-setup github repostiory > And please assign igoihman as administrator. > Thanks. > [~igoihman(a)redhat.com] > [~mwperina] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076) ------------=_1516632284-28099-266 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1857?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1857:</h3> <pre>Status: In Progress (was: To Do)</pre> <blockquote><h3>Please create ovirt-ansible-dpdk-setup github repostiory</h3> <pre> Key: OVIRT-1857 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1857 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ondra Machacek Assignee: infra</pre> <p>Please create ovirt-ansible-dpdk-setup github repostiory And please assign igoihman as administrator. Thanks. [~igoihman(a)redhat.com] [~mwperina]</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1516632284-28099-266--

1 0

Last week for participating to oVirt 2018 Survey!
by Sandro Bonazzola 22 Jan '18

22 Jan '18

As we continue to develop oVirt 4.2 and future releases, the Development and Integration teams at Red Hat would value insights on how you are deploying the oVirt environment. If you haven't already done, please help us to hit the mark by completing this short survey. Survey will close on February 1st. Here's the link to the survey: https://goo.gl/forms/cAKWAR8RD7rGrVhE2 Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[JIRA] (OVIRT-1858) upgrade jenkins.ovirt.org to 2.89.3 LTS
by Evgheni Dereveanchin (oVirt JIRA) 22 Jan '18

22 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1858?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1858: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to 2.89.3 LTS > --------------------------------------- > > Key: OVIRT-1858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1858 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins 2.89.3 LTS is out, our instance needs to be updated. > There is also a new security advisory out so we will bump plugin versions: > https://jenkins.io/security/advisory/2018-01-22/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1858) upgrade jenkins.ovirt.org to 2.89.3 LTS
by Evgheni Dereveanchin (oVirt JIRA) 22 Jan '18

22 Jan '18

Evgheni Dereveanchin created OVIRT-1858: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to 2.89.3 LTS Key: OVIRT-1858 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1858 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Jenkins 2.89.3 LTS is out, our instance needs to be updated. There is also a new security advisory out so we will bump plugin versions: https://jenkins.io/security/advisory/2018-01-22/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1857) Please create ovirt-ansible-dpdk-setup github repostiory
by Ondra Machacek (oVirt JIRA) 22 Jan '18

22 Jan '18

Ondra Machacek created OVIRT-1857: ------------------------------------- Summary: Please create ovirt-ansible-dpdk-setup github repostiory Key: OVIRT-1857 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1857 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ondra Machacek Assignee: infra Please create ovirt-ansible-dpdk-setup github repostiory And please assign igoihman as administrator. Thanks. [~igoihman(a)redhat.com] [~mwperina] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[ OST Failure Report ] [ oVirt hc master ] [ 19-01-2018 ] [ 002_bootstrap.add_hosts ]
by Dafna Ron 22 Jan '18

22 Jan '18

Hi, we are failing hc master basic suite on test: 002_bootstrap.add_hosts *Link and headline of suspected patches: Link to Job:http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/1… <http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/163/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/… <http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/163/a…>(Relevant) error snippet from the log: <error>*2018-01-18 22:30:56,141-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [3e58f8ce] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host lago_basic_suite_hc_host0: Failed to execute stage 'Closing up': 'Plugin' object has no attribute 'exist' *</error>*

3 2

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 678 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jan '18

21 Jan '18

------=_Part_193_634794444.1516455686513 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build Number: 678 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #678 [Sandro Bonazzola] automation: check and save unsigned rpms ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_193_634794444.1516455686513--

1 1

[JIRA] (OVIRT-1856) Document procedure for infra upgrades
by eyal edri (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1856?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1856: ----------------------------- Priority: High (was: Medium) > Document procedure for infra upgrades > -------------------------------------- > > Key: OVIRT-1856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1856 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: infra > Priority: High > > On Sun, Jan 21, 2018 at 1:01 PM, Barak Korren <bkorren(a)redhat.com> wrote: > > > > > > On 21 January 2018 at 12:50, Eyal Edri <eedri(a)redhat.com> wrote: > > > >> > >> > >> On Sun, Jan 21, 2018 at 12:47 PM, Barak Korren <bkorren(a)redhat.com> > >> wrote: > >> > >>> > >>> > >>> On 21 January 2018 at 12:39, Eyal Edri <eedri(a)redhat.com> wrote: > >>> > >>>> There is another issue, which is currently failing all CQ, and its > >>>> related to the new IBRS CPU model. > >>>> It looks like all of the lago slaves were upgraded to new Libvirt and > >>>> kernel on Friday, while we still don't have a fix on lago-ost-plugin for > >>>> that. > >>>> > >>>> I think there was a misunderstanding about what to upgrade, and it > >>>> might have been understood that only the bios upgrade breaks it and not the > >>>> kernel one. > >>>> > >>>> In any case, we're currently fixing the issue, either by downgrading > >>>> the relevant pkgs on lago slaves or adding the mapping to new CPU types > >>>> from OST. > >>>> > >>>> For future, I suggest a few updates to maintenance work on Jenkins > >>>> slaves ( VMs or BM ): > >>>> > >>>> 1. Let's avoid doing an upgrade close to a weekend ( i.e not on Thu-Sun > >>>> ), so all the team can be around to help if needed or if something > >>>> unexpected happens. > >>>> 2. When we have a system-wide upgrade scheduled, like all BM slaves or > >>>> VMs for a specific OS, let's adopt a gradual upgrade with a few days window > >>>> in between, > >>>> e.g, if we need to upgrade all Lago slaves, let's upgrade 1-2 and > >>>> wait to see if nothing breaks and continue after we verify OST runs ( > >>>> either seeing on CQ or running manually ) > >>>> > >>>> > >>>> Thoughts? > >>>> > >>>> > >>> We have a staging system - we should be using it for staging.... > >>> > >> > >> Do we have OST tests or manual job avaialble there? > >> > > > > We can add them easily, or simply run Lago manually when needed. > > > > > >> In any case, this doesn't contradict what I suggested, even if you test > >> on staging, there could be differences from the production system, so we > >> should take care when we upgrade regardless. > >> > > > > Yes, but at least we'd know we green lighted the new configuration - I'm > > sure in this case we could have found at least some of the issues on > > staging (Like the fc27 issues for example) and could have avoided expansive > > production failures. > > > > Another point when scheduling an upgrade, is to talk to infra owner or the > >> CI team and understand if we currently have a large Q in CQ or known > >> failures, so it might be best to wait a bit until its cleared. > >> > >> > > > > > Adding infra-support so we can gather this info and prepare a maintanaince > / upgrade checklist to add to the oVirt infra docs. > Let's continue the discussion, suggestion on that ticket. > > -- > > Barak Korren > > RHV DevOps team , RHCE, RHCi > > Red Hat EMEA > > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1856) Document procedure for infra upgrades
by eyal edri (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1856?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1856: ----------------------------- Summary: Document procedure for infra upgrades (was: Re: Change-queue job failures this weekend) > Document procedure for infra upgrades > -------------------------------------- > > Key: OVIRT-1856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1856 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: infra > > On Sun, Jan 21, 2018 at 1:01 PM, Barak Korren <bkorren(a)redhat.com> wrote: > > > > > > On 21 January 2018 at 12:50, Eyal Edri <eedri(a)redhat.com> wrote: > > > >> > >> > >> On Sun, Jan 21, 2018 at 12:47 PM, Barak Korren <bkorren(a)redhat.com> > >> wrote: > >> > >>> > >>> > >>> On 21 January 2018 at 12:39, Eyal Edri <eedri(a)redhat.com> wrote: > >>> > >>>> There is another issue, which is currently failing all CQ, and its > >>>> related to the new IBRS CPU model. > >>>> It looks like all of the lago slaves were upgraded to new Libvirt and > >>>> kernel on Friday, while we still don't have a fix on lago-ost-plugin for > >>>> that. > >>>> > >>>> I think there was a misunderstanding about what to upgrade, and it > >>>> might have been understood that only the bios upgrade breaks it and not the > >>>> kernel one. > >>>> > >>>> In any case, we're currently fixing the issue, either by downgrading > >>>> the relevant pkgs on lago slaves or adding the mapping to new CPU types > >>>> from OST. > >>>> > >>>> For future, I suggest a few updates to maintenance work on Jenkins > >>>> slaves ( VMs or BM ): > >>>> > >>>> 1. Let's avoid doing an upgrade close to a weekend ( i.e not on Thu-Sun > >>>> ), so all the team can be around to help if needed or if something > >>>> unexpected happens. > >>>> 2. When we have a system-wide upgrade scheduled, like all BM slaves or > >>>> VMs for a specific OS, let's adopt a gradual upgrade with a few days window > >>>> in between, > >>>> e.g, if we need to upgrade all Lago slaves, let's upgrade 1-2 and > >>>> wait to see if nothing breaks and continue after we verify OST runs ( > >>>> either seeing on CQ or running manually ) > >>>> > >>>> > >>>> Thoughts? > >>>> > >>>> > >>> We have a staging system - we should be using it for staging.... > >>> > >> > >> Do we have OST tests or manual job avaialble there? > >> > > > > We can add them easily, or simply run Lago manually when needed. > > > > > >> In any case, this doesn't contradict what I suggested, even if you test > >> on staging, there could be differences from the production system, so we > >> should take care when we upgrade regardless. > >> > > > > Yes, but at least we'd know we green lighted the new configuration - I'm > > sure in this case we could have found at least some of the issues on > > staging (Like the fc27 issues for example) and could have avoided expansive > > production failures. > > > > Another point when scheduling an upgrade, is to talk to infra owner or the > >> CI team and understand if we currently have a large Q in CQ or known > >> failures, so it might be best to wait a bit until its cleared. > >> > >> > > > > > Adding infra-support so we can gather this info and prepare a maintanaince > / upgrade checklist to add to the oVirt infra docs. > Let's continue the discussion, suggestion on that ticket. > > -- > > Barak Korren > > RHV DevOps team , RHCE, RHCi > > Red Hat EMEA > > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1856) Re: Change-queue job failures this weekend
by Daniel Belenky (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1856?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1856: --------------------------------------- As for now, [tester 5029|http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_c…] passed with 175 patches. So for now, we know that there are no unknown regressions in master repo. > Re: Change-queue job failures this weekend > ------------------------------------------ > > Key: OVIRT-1856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1856 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: infra > > On Sun, Jan 21, 2018 at 1:01 PM, Barak Korren <bkorren(a)redhat.com> wrote: > > > > > > On 21 January 2018 at 12:50, Eyal Edri <eedri(a)redhat.com> wrote: > > > >> > >> > >> On Sun, Jan 21, 2018 at 12:47 PM, Barak Korren <bkorren(a)redhat.com> > >> wrote: > >> > >>> > >>> > >>> On 21 January 2018 at 12:39, Eyal Edri <eedri(a)redhat.com> wrote: > >>> > >>>> There is another issue, which is currently failing all CQ, and its > >>>> related to the new IBRS CPU model. > >>>> It looks like all of the lago slaves were upgraded to new Libvirt and > >>>> kernel on Friday, while we still don't have a fix on lago-ost-plugin for > >>>> that. > >>>> > >>>> I think there was a misunderstanding about what to upgrade, and it > >>>> might have been understood that only the bios upgrade breaks it and not the > >>>> kernel one. > >>>> > >>>> In any case, we're currently fixing the issue, either by downgrading > >>>> the relevant pkgs on lago slaves or adding the mapping to new CPU types > >>>> from OST. > >>>> > >>>> For future, I suggest a few updates to maintenance work on Jenkins > >>>> slaves ( VMs or BM ): > >>>> > >>>> 1. Let's avoid doing an upgrade close to a weekend ( i.e not on Thu-Sun > >>>> ), so all the team can be around to help if needed or if something > >>>> unexpected happens. > >>>> 2. When we have a system-wide upgrade scheduled, like all BM slaves or > >>>> VMs for a specific OS, let's adopt a gradual upgrade with a few days window > >>>> in between, > >>>> e.g, if we need to upgrade all Lago slaves, let's upgrade 1-2 and > >>>> wait to see if nothing breaks and continue after we verify OST runs ( > >>>> either seeing on CQ or running manually ) > >>>> > >>>> > >>>> Thoughts? > >>>> > >>>> > >>> We have a staging system - we should be using it for staging.... > >>> > >> > >> Do we have OST tests or manual job avaialble there? > >> > > > > We can add them easily, or simply run Lago manually when needed. > > > > > >> In any case, this doesn't contradict what I suggested, even if you test > >> on staging, there could be differences from the production system, so we > >> should take care when we upgrade regardless. > >> > > > > Yes, but at least we'd know we green lighted the new configuration - I'm > > sure in this case we could have found at least some of the issues on > > staging (Like the fc27 issues for example) and could have avoided expansive > > production failures. > > > > Another point when scheduling an upgrade, is to talk to infra owner or the > >> CI team and understand if we currently have a large Q in CQ or known > >> failures, so it might be best to wait a bit until its cleared. > >> > >> > > > > > Adding infra-support so we can gather this info and prepare a maintanaince > / upgrade checklist to add to the oVirt infra docs. > Let's continue the discussion, suggestion on that ticket. > > -- > > Barak Korren > > RHV DevOps team , RHCE, RHCi > > Red Hat EMEA > > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1856) Re: Change-queue job failures this weekend
by eyal edri (oVirt JIRA) 21 Jan '18

21 Jan '18

eyal edri created OVIRT-1856: -------------------------------- Summary: Re: Change-queue job failures this weekend Key: OVIRT-1856 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1856 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri Assignee: infra On Sun, Jan 21, 2018 at 1:01 PM, Barak Korren <bkorren(a)redhat.com> wrote: > > > On 21 January 2018 at 12:50, Eyal Edri <eedri(a)redhat.com> wrote: > >> >> >> On Sun, Jan 21, 2018 at 12:47 PM, Barak Korren <bkorren(a)redhat.com> >> wrote: >> >>> >>> >>> On 21 January 2018 at 12:39, Eyal Edri <eedri(a)redhat.com> wrote: >>> >>>> There is another issue, which is currently failing all CQ, and its >>>> related to the new IBRS CPU model. >>>> It looks like all of the lago slaves were upgraded to new Libvirt and >>>> kernel on Friday, while we still don't have a fix on lago-ost-plugin for >>>> that. >>>> >>>> I think there was a misunderstanding about what to upgrade, and it >>>> might have been understood that only the bios upgrade breaks it and not the >>>> kernel one. >>>> >>>> In any case, we're currently fixing the issue, either by downgrading >>>> the relevant pkgs on lago slaves or adding the mapping to new CPU types >>>> from OST. >>>> >>>> For future, I suggest a few updates to maintenance work on Jenkins >>>> slaves ( VMs or BM ): >>>> >>>> 1. Let's avoid doing an upgrade close to a weekend ( i.e not on Thu-Sun >>>> ), so all the team can be around to help if needed or if something >>>> unexpected happens. >>>> 2. When we have a system-wide upgrade scheduled, like all BM slaves or >>>> VMs for a specific OS, let's adopt a gradual upgrade with a few days window >>>> in between, >>>> e.g, if we need to upgrade all Lago slaves, let's upgrade 1-2 and >>>> wait to see if nothing breaks and continue after we verify OST runs ( >>>> either seeing on CQ or running manually ) >>>> >>>> >>>> Thoughts? >>>> >>>> >>> We have a staging system - we should be using it for staging.... >>> >> >> Do we have OST tests or manual job avaialble there? >> > > We can add them easily, or simply run Lago manually when needed. > > >> In any case, this doesn't contradict what I suggested, even if you test >> on staging, there could be differences from the production system, so we >> should take care when we upgrade regardless. >> > > Yes, but at least we'd know we green lighted the new configuration - I'm > sure in this case we could have found at least some of the issues on > staging (Like the fc27 issues for example) and could have avoided expansive > production failures. > > Another point when scheduling an upgrade, is to talk to infra owner or the >> CI team and understand if we currently have a large Q in CQ or known >> failures, so it might be best to wait a bit until its cleared. >> >> > > Adding infra-support so we can gather this info and prepare a maintanaince / upgrade checklist to add to the oVirt infra docs. Let's continue the discussion, suggestion on that ticket. > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

Change-queue job failures this weekend
by Barak Korren 21 Jan '18

21 Jan '18

Hi, We seen a great deal of noise coming from the change queue this weekend. While a part of it is due to actual code regressions, some of that was actually due to two separate infra issues. One issue we had was with building FC26 packages - it turns out that a yum-incompatible update if the 'cmake' package was introduced to the FC26 updates repo. Since for the time being we use 'yum' to setup the mock environments, the build jobs for FC26 started failing. This issue was actually reported to us [1]. To resolve this - we rolled back the FC26 mirror to a time before the breaking change was introduced, and then re-triggered the merge events for all the patches that failed building to introduce passing build to the change queue. The second issue had to do with the introduction of FC27 slaves - it seems that slaves were misconfigured [2] and did not include vary basic packages like 'git' - this caused the CQ master job to simply crash and stop queue processing. To resolve this issue we disabled the FC27 slaves, resumed CQ operation and then re-sent all changes that failed to be added into the queue. We are in the final phases of integrating a new oVirt release, so proper CQ operation is crucial at this time. Additionally, due to a substantial amount of regressions introduced last week, the CQ currently has a huge backlog of ~180 changes to work through, this means that every bisection takes 8 OST runs, so we have no CQ minutes to spare. The FC27 slaves issue cost us 11 hours in which the CQ was not running. It also manifested itself in failures of the 'standard-enqueue' job. These kinds of failures need to be handled promptly or be avoided altogether. Build failures can make the CQ waste time too, as it runs bisections to detect and remove changes that fail to build. At this time, a single failed build can waste up to 8 hours! Lets try to be more careful about introducing infrastructure changes to the system at sensitive times, and be more vigilant about failure reports from jenkins. [1]: https://ovirt-jira.atlassian.net/browse/OVIRT-1854 [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-1855 -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

3 6

[CQ]: 86329, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jan '18

21 Jan '18

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

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 141 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jan '18

21 Jan '18

------=_Part_191_1316440095.1516441554553 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artifac… Build Number: 141 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #141 [Yuval Turgeman] scripts: timeout when waiting for vm to install ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_191_1316440095.1516441554553--

1 1

[CQ]: 86552,1 (ovirt-log-collector) failed "ovirt-4.2" system tests
by oVirt Jenkins 21 Jan '18

21 Jan '18

Change 86552,1 (ovirt-log-collector) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/86552/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/261/

4 7

[CQ]: 86453,2 (ovirt-engine) failed "ovirt-4.1" system tests
by oVirt Jenkins 21 Jan '18

21 Jan '18

Change 86453,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/86453/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1525/

1 0

[CQ]: 86337, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jan '18

21 Jan '18

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

2 1

[JIRA] (OVIRT-1855) outage in all fc27 slaves
by Daniel Belenky (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1855?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1855: ------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > outage in all fc27 slaves > ------------------------- > > Key: OVIRT-1855 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1855 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Jenkins Slaves > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > Hi, > During the weekend all fc27 slaves were not configured properly (some basic packages such as git were missing). > This caused some noise on our CQ jobs. > Currently, I've set all fc27 slaves offline until we'll fix them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1855) outage in all fc27 slaves
by Daniel Belenky (oVirt JIRA) 21 Jan '18

21 Jan '18

This is a multi-part message in MIME format... ------------=_1516522203-19290-211 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Daniel Belenky created OVIRT-1855: ------------------------------------- Summary: outage in all fc27 slaves Key: OVIRT-1855 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1855 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue, Jenkins Slaves Reporter: Daniel Belenky Assignee: infra Hi, During the weekend all fc27 slaves were not configured properly (some basic packages such as git were missing). This caused some noise on our CQ jobs. Currently, I've set all fc27 slaves offline until we'll fix them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076) ------------=_1516522203-19290-211 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Daniel Belenky created OVIRT-1855:</h3> <pre> Summary: outage in all fc27 slaves Key: OVIRT-1855 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1855 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue, Jenkins Slaves Reporter: Daniel Belenky Assignee: infra</pre> <p>Hi,</p> <p>During the weekend all fc27 slaves were not configured properly (some basic packages such as git were missing). This caused some noise on our CQ jobs.</p> <p>Currently, I've set all fc27 slaves offline until we'll fix them.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1516522203-19290-211--

1 0

[JIRA] (OVIRT-1855) outage in all fc27 slaves
by Daniel Belenky (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1855?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1855: ---------------------------------- Epic Link: OVIRT-403 > outage in all fc27 slaves > ------------------------- > > Key: OVIRT-1855 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1855 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Jenkins Slaves > Reporter: Daniel Belenky > Assignee: infra > > Hi, > During the weekend all fc27 slaves were not configured properly (some basic packages such as git were missing). > This caused some noise on our CQ jobs. > Currently, I've set all fc27 slaves offline until we'll fix them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[CQ]: 86592, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jan '18

21 Jan '18

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

1 0

[JIRA] (OVIRT-1849) enable all gerrit hooks for cockpit-ovirt project
by eyal edri (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1849?page=com.atlassian.jira.… ] eyal edri edited comment on OVIRT-1849 at 1/21/18 7:07 AM: ----------------------------------------------------------- [~amarchuk][~dfodor] let me know if you need help, the instructions on how to enable more hooks are in the link added to the ticket DESC. was (Author: eedri): [~amarchuk][~dfodor] letme know if you need help, the instructions on how to enable more hooks are in the link added to the ticket DESC. > enable all gerrit hooks for cockpit-ovirt project > ------------------------------------------------- > > Key: OVIRT-1849 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1849 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > > It looks like the cockpit-ovirt project doesn't have all hooks enabled, current these are the hooks its using: > /home/gerrit2/review_site/hooks/custom_hooks/update_tracker > /home/gerrit2/review_site/hooks/custom_hooks/comment-added.propagate_review_values > If we want that the hooks will also update bz status and do other verification like backporing, we need to add more hooks. > [~sbonazzo(a)redhat.com] [~msivak(a)redhat.com] please comment which hooks you'd like to enable or all of them. > Info on the hooks can be found here :http://ovirt-infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Projects/index.html#enabling-custom-gerrit-hooks > [~amarchuk] fyi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1849) enable all gerrit hooks for cockpit-ovirt project
by eyal edri (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1849?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1849: ---------------------------------- [~amarchuk][~dfodor] letme know if you need help, the instructions on how to enable more hooks are in the link added to the ticket DESC. > enable all gerrit hooks for cockpit-ovirt project > ------------------------------------------------- > > Key: OVIRT-1849 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1849 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > > It looks like the cockpit-ovirt project doesn't have all hooks enabled, current these are the hooks its using: > /home/gerrit2/review_site/hooks/custom_hooks/update_tracker > /home/gerrit2/review_site/hooks/custom_hooks/comment-added.propagate_review_values > If we want that the hooks will also update bz status and do other verification like backporing, we need to add more hooks. > [~sbonazzo(a)redhat.com] [~msivak(a)redhat.com] please comment which hooks you'd like to enable or all of them. > Info on the hooks can be found here :http://ovirt-infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Projects/index.html#enabling-custom-gerrit-hooks > [~amarchuk] fyi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1854) fc26 dashboard jobs failing on rpm install for cmake-data and cmake
by Daniel Belenky (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1854?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1854: ------------------------------------- Assignee: Daniel Belenky (was: infra) > fc26 dashboard jobs failing on rpm install for cmake-data and cmake > ------------------------------------------------------------------- > > Key: OVIRT-1854 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1854 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Daniel Belenky > > Hi, > Anyone seen anything like this? > http://jenkins.ovirt.org/job/ovirt-engine-dashboard_master_check-merged-fc2… > 17:45:32 --> Processing Dependency: (cmake = 3.10.1-11.fc26 if cmake < > 3.10.1-11.fc26) for package: cmake-rpm-macros-3.10.1-11.fc26.noarch > 17:45:32 ---> Package device-mapper.x86_64 0:1.02.137-6.fc26 will be > installed > 17:45:32 --> Finished Dependency Resolution > 17:45:32 Error: Package: cmake-rpm-macros-3.10.1-11.fc26.noarch > (fedora-updates-fc26) > 17:45:32 Requires: (cmake-data = 3.10.1-11.fc26 if cmake-data < > 3.10.1-11.fc26) > 17:45:32 You could try using --skip-broken to work around the problem > 17:45:32 Error: Package: cmake-rpm-macros-3.10.1-11.fc26.noarch > (fedora-updates-fc26) > 17:45:32 Requires: (cmake = 3.10.1-11.fc26 if cmake < > 3.10.1-11.fc26) > 17:45:32 You could try running: rpm -Va --nofiles --nodigest > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[JIRA] (OVIRT-1854) fc26 dashboard jobs failing on rpm install for cmake-data and cmake
by Daniel Belenky (oVirt JIRA) 21 Jan '18

21 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1854?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1854: ---------------------------------- Status: In Progress (was: To Do) > fc26 dashboard jobs failing on rpm install for cmake-data and cmake > ------------------------------------------------------------------- > > Key: OVIRT-1854 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1854 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Anyone seen anything like this? > http://jenkins.ovirt.org/job/ovirt-engine-dashboard_master_check-merged-fc2… > 17:45:32 --> Processing Dependency: (cmake = 3.10.1-11.fc26 if cmake < > 3.10.1-11.fc26) for package: cmake-rpm-macros-3.10.1-11.fc26.noarch > 17:45:32 ---> Package device-mapper.x86_64 0:1.02.137-6.fc26 will be > installed > 17:45:32 --> Finished Dependency Resolution > 17:45:32 Error: Package: cmake-rpm-macros-3.10.1-11.fc26.noarch > (fedora-updates-fc26) > 17:45:32 Requires: (cmake-data = 3.10.1-11.fc26 if cmake-data < > 3.10.1-11.fc26) > 17:45:32 You could try using --skip-broken to work around the problem > 17:45:32 Error: Package: cmake-rpm-macros-3.10.1-11.fc26.noarch > (fedora-updates-fc26) > 17:45:32 Requires: (cmake = 3.10.1-11.fc26 if cmake < > 3.10.1-11.fc26) > 17:45:32 You could try running: rpm -Va --nofiles --nodigest > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[CQ]: 85224,12 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 20 Jan '18

20 Jan '18

Change 85224,12 (ovirt-engine) 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/85224/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5008/

1 0

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

20 Jan '18

A system test invoked by the "ovirt-master" change queue including change ef965b9 (ovirt-ansible-disaster-recovery) failed. However, this change seems not to be the root cause for this failure. Change 6f46b0a (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 6f46b0a (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/ef965b93237… 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/6f46b0a5f93… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5000/

1 0