- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

Failed to run project_setup.sh for: #41. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-dx3hf.

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

Failed to run project_setup.sh for: #38. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-glcxl.

1 0

[CQ]: 103041, 8 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

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

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

Failed to run project_setup.sh for: #35. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-crhwl.

1 0

[JIRA] (OVIRT-2788) CI: Add the option to send and email if stage fails
by Eyal Edri (oVirt JIRA) 04 Sep '19

04 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2788?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2788: ---------------------------------- [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] [~accountid:5aa0f39f5a4d022884128a0f] Can you assist? where is the email definition for upstream sources is done ? > CI: Add the option to send and email if stage fails > --------------------------------------------------- > > Key: OVIRT-2788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2788 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Bell Levin > Assignee: infra > > Added the poll-upstream-sources stage to be ran every night on vdsm \[1]. I think it is useful if an email is sent to selected people if the stage has failed. > Such option is available in V1 (namely, the nightly ost network suite), and would help me out if implemented in V2 as well. > \[1] [https://gerrit.ovirt.org/#/c/102901/|https://gerrit.ovirt.org/#/c/102901/] > FYI [~accountid:557058:866c109f-3951-4680-8dac-b76caf296501] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] [~accountid:5aa0f39f5a4d022884128a0f] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dpati@redhat.com from infra@ovirt.org ?
by Eyal Edri (oVirt JIRA) 04 Sep '19

04 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2789?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2789: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Fwd: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? > ---------------------------------------------------------------------- > > Key: OVIRT-2789 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2789 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: infra > > Forwarding to infra-support, so Duck will see this. > ---------- Forwarded message --------- > From: Yaniv Kaul <ykaul(a)redhat.com> > Date: Tue, 3 Sep 2019 at 16:34 > Subject: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? > To: Barak Korren <bkorren(a)redhat.com> > He no longer works at Red Hat and neither his manager - and I'm getting > those emails, without the ability to remove him (or her?). > TIA, > Y. > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dpati@redhat.com from infra@ovirt.org ?
by Eyal Edri (oVirt JIRA) 04 Sep '19

04 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2789?page=com.atlassian.jira.… ] Eyal Edri edited comment on OVIRT-2789 at 9/4/19 3:21 PM: ---------------------------------------------------------- Done. removed him from infra list via the admin interface on lists.ovirt.org was (Author: eedri): Done. removed him from infra list via the admin interface on lists.redhat.com > Fwd: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? > ---------------------------------------------------------------------- > > Key: OVIRT-2789 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2789 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: infra > > Forwarding to infra-support, so Duck will see this. > ---------- Forwarded message --------- > From: Yaniv Kaul <ykaul(a)redhat.com> > Date: Tue, 3 Sep 2019 at 16:34 > Subject: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? > To: Barak Korren <bkorren(a)redhat.com> > He no longer works at Red Hat and neither his manager - and I'm getting > those emails, without the ability to remove him (or her?). > TIA, > Y. > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dpati@redhat.com from infra@ovirt.org ?
by Eyal Edri (oVirt JIRA) 04 Sep '19

04 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2789?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2789: ---------------------------------- Done. removed him from infra list via the admin interface on lists.redhat.com > Fwd: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? > ---------------------------------------------------------------------- > > Key: OVIRT-2789 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2789 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: infra > > Forwarding to infra-support, so Duck will see this. > ---------- Forwarded message --------- > From: Yaniv Kaul <ykaul(a)redhat.com> > Date: Tue, 3 Sep 2019 at 16:34 > Subject: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? > To: Barak Korren <bkorren(a)redhat.com> > He no longer works at Red Hat and neither his manager - and I'm getting > those emails, without the ability to remove him (or her?). > TIA, > Y. > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

Failed to run project_setup.sh for: #32. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-rdnht.

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

Failed to run project_setup.sh for: #29. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-3nkl9.

1 0

[CQ]: d1d35ca (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change d1d35ca (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 66bcd08 (ovirt-web-ui) 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 66bcd08 (ovirt-web-ui) 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-web-ui/commit/d1d35ca3fed49848306626926ac80a… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/66bcd087851d4c49f0c7037d599888… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4778/

1 0

[CQ]: 102843, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

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

1 0

[CQ]: 103040, 1 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests
by oVirt Jenkins 04 Sep '19

04 Sep '19

Change 103040,1 (ovirt-engine-ui-extensions) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/103040/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1985/

1 0

[CQ]: 103034, 2 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

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

1 0

[CQ]: 102024, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

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

1 0

Re: [ovirt-users] the virtual machine crushed and I cant shutdown the vm successfully
by Liran Rotenberg 04 Sep '19

04 Sep '19

Hi, Can you try to upgrade the kernel both on the guest and the host? Also, consider upgrade to 4.3 since 4.2 is EOL. Regards, Liran. On Wed, Sep 4, 2019 at 9:57 AM zhouhao(a)vip.friendtimes.net < zhouhao(a)vip.friendtimes.net> wrote: > > Dear ovirt developers: > The trouble bothered me for a long time;Some times my vm will > crush and I cant shutdown it,I had to reboot the ovirt-node to slove it; > the vm's error below > > The ovirt-node's error below > > The vm's threading on the ovirt-node, the IO ratio is 100% > > > and the vm's process change to defunct > I can not kill it,every time I had to shutdown the ovirt-node > > on the engine website ,the vm's status always in the way to shutdown > ,even if I wait for it for hours; > It either failed or is shutting down > and the "power off" cant shutdown the vm too. > > ---------------------------------------------------------------- > The other infomation about my ovirt-node > node-version： > node hardware > > > > > > ------------------------------ > zhouhao(a)vip.friendtimes.net > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/6NORRN45W25D6… >

1 0

[CQ]: 101710, 13 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 182 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/182/ Build Number: 182 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #182 [arachmani] 008_basic_ui_sanity: Change selenium image [Barak Korren] gate: Filter releases by change queue prefix ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 101745, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

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

1 0

[CQ]: 103057, 6 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '19

04 Sep '19

A system test invoked by the "ovirt-4.3" change queue including change 103057,6 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102982,4 (ovirt-engine-nodejs-modules) 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 102982,4 (ovirt-engine-nodejs- modules) 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/103057/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102982/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1976/

1 0

oVirt infra daily report - unstable production jobs - 937
by jenkins＠jenkins.phx.ovirt.org 04 Sep '19

04 Sep '19

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

1 0

[CQ]: 103028, 2 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[CQ]: 101709, 14 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #26. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-hc3jc.

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Barak Korren (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2790: -------------------------------- Resolution: Fixed Status: Done (was: To Do) > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Barak Korren (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2790: ------------------------------------- I see, maybe put a cheat sheet for him somewhere... closing the ticket now > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 103048,1 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[CQ]: 101708, 14 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[CQ]: f619e0e (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change f619e0e (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 5a784af (ovirt-ansible-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 5a784af (ovirt-ansible-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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/f619e0e8d… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/5a784af36… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4776/

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Artur Socha (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Artur Socha commented on OVIRT-2790: ------------------------------------ Oh, that is even better - thanks Barak\! [~accountid:557058:7013bb8c-48b2-4b9b-898e-eccf5fb61fad] told me. > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 5a784af (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 03 Sep '19

03 Sep '19

Change 5a784af (ovirt-ansible-hosted-engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/5a784af36… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4775/

1 0

[CQ]: 103053, 2 (ovirt-host-deploy) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Barak Korren (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2790: ------------------------------------- If all you want to do is to re-run - you can just type {{ci test please}} into a comment on your patch Where did you find the instructions for using the manual trigger? we might need to update it? > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Artur Socha (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Artur Socha updated OVIRT-2790: ------------------------------- Description: Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] Thanks\! was: Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) Thanks! > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Artur Socha (oVirt JIRA) 03 Sep '19

03 Sep '19

Artur Socha created OVIRT-2790: ---------------------------------- Summary: Jenkins: build manual trigger rights for asocha Key: OVIRT-2790 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 Project: oVirt - virtualization made easy Issue Type: Task Components: Jenkins Master Reporter: Artur Socha Assignee: infra Priority: Low Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) Thanks! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dpati@redhat.com from infra@ovirt.org ?
by Barak Korren (oVirt JIRA) 03 Sep '19

03 Sep '19

Barak Korren created OVIRT-2789: ----------------------------------- Summary: Fwd: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? Key: OVIRT-2789 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2789 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support, so Duck will see this. ---------- Forwarded message --------- From: Yaniv Kaul <ykaul(a)redhat.com> Date: Tue, 3 Sep 2019 at 16:34 Subject: Any chance you can remove dpati(a)redhat.com from infra(a)ovirt.org ? To: Barak Korren <bkorren(a)redhat.com> He no longer works at Red Hat and neither his manager - and I'm getting those emails, without the ability to remove him (or her?). TIA, Y. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2788) CI: Add the option to send and email if stage fails
by Bell Levin (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2788?page=com.atlassian.jira.… ] Bell Levin updated OVIRT-2788: ------------------------------ Description: Added the poll-upstream-sources stage to be ran every night on vdsm \[1]. I think it is useful if an email is sent to selected people if the stage has failed. Such option is available in V1 (namely, the nightly ost network suite), and would help me out if implemented in V2 as well. \[1] [https://gerrit.ovirt.org/#/c/102901/|https://gerrit.ovirt.org/#/c/102901/] FYI [~accountid:557058:866c109f-3951-4680-8dac-b76caf296501] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] [~accountid:5aa0f39f5a4d022884128a0f] was: Added the poll-upstream-sources stage to be ran every night on vdsm [1]. I think it is useful if an email is sent to selected people if the stage has failed. Such option is available in V1 (namely, the nightly ost network suite), and would help me out if implemented in V2 as well. [1] https://gerrit.ovirt.org/#/c/102901/ FYI [~accountid:557058:866c109f-3951-4680-8dac-b76caf296501] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] > CI: Add the option to send and email if stage fails > --------------------------------------------------- > > Key: OVIRT-2788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2788 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Bell Levin > Assignee: infra > > Added the poll-upstream-sources stage to be ran every night on vdsm \[1]. I think it is useful if an email is sent to selected people if the stage has failed. > Such option is available in V1 (namely, the nightly ost network suite), and would help me out if implemented in V2 as well. > \[1] [https://gerrit.ovirt.org/#/c/102901/|https://gerrit.ovirt.org/#/c/102901/] > FYI [~accountid:557058:866c109f-3951-4680-8dac-b76caf296501] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] [~accountid:5aa0f39f5a4d022884128a0f] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2788) CI: Add the option to send and email if stage fails
by Bell Levin (oVirt JIRA) 03 Sep '19

03 Sep '19

Bell Levin created OVIRT-2788: --------------------------------- Summary: CI: Add the option to send and email if stage fails Key: OVIRT-2788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2788 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI client projects Reporter: Bell Levin Assignee: infra Added the poll-upstream-sources stage to be ran every night on vdsm [1]. I think it is useful if an email is sent to selected people if the stage has failed. Such option is available in V1 (namely, the nightly ost network suite), and would help me out if implemented in V2 as well. [1] https://gerrit.ovirt.org/#/c/102901/ FYI [~accountid:557058:866c109f-3951-4680-8dac-b76caf296501] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 103057, 6 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3291 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0163.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3290 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0062.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3290 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0038.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3290 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0040.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3290 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0047.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3290 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0090.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Sep '19

03 Sep '19

Failed to run project_setup.sh for: #3290 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0219.workers-phx.ovirt.org.

1 0

[CQ]: 103052,2 (ovirt-host-deploy) failed "ovirt-4.3" system tests
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[CQ]: 102914, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot
by Anton Marchukov (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2786: ----------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: fc30 packages in master snapshot > ------------------------------------ > > Key: OVIRT-2786 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Adding infra-support to open a ticket. > > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > > > Hi, > > > > How are these published? > > > > A few days ago we merged patches to add fc30 builds of otopi and > > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > > good. But we do not see them in [1]. Should we? Are they stuck > > somewhere, or there is simply nothing that publishes them these days? > > Asking the latter, because the timestamps on the few files there are > > from more than 3 months ago. > > > > Thanks and best regards, > > > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > > -- > > Didi > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2787) connecting to ci slave as developer account
by Anton Marchukov (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2787?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2787: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) This is generally not possible as the infrastructure is ephemeral, the way to do it is to run CI locally and/or have logs good enough to get the idea out of it. In complex cases feel free to reach us for specific case, so we can help. > connecting to ci slave as developer account > ------------------------------------------- > > Key: OVIRT-2787 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Or Shoval > Assignee: infra > > Hi Infra, > sometimes in CNV we are using CI, > and stuff fails, > it would be awesome if we can get a developer profile > that allows to connect in a restricted shell / rbash (idea by Dafna) > in order to execute commands like get pods and describe pods, > that will give hint about the problems > is it possible please ? what it involves > it can reduce lot of time and effort > thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0