September 2019 - Infra - oVirt List Archives

[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