- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 1022
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '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/1022//artifact/exported-… Cheers, Jenkins

1 0

[CQ]: 103737, 35 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #6610 ovirt-system-tests [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 openshift-integ-tests-container-rdc02.

1 0

[CQ]: 103615, 20 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_gate
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #211. 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-mdzhk.

1 0

[CQ]: 103618, 35 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #306 ovirt-engine-ui-extensions [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #304 ovirt-engine-ui-extensions [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 vm0009.workers-phx.ovirt.org.

1 1

[CQ]: 103616, 32 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #15075 vdsm [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 vm0009.workers-phx.ovirt.org.

1 0

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

27 Nov '19

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

1 0

[JIRA] (OVIRT-2843) Whitlisting users for CI on GitHub does not work
by Barak Korren (oVirt JIRA) 27 Nov '19

27 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2843?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2843: ----------------------------------- Assignee: Barak Korren (was: infra) > Whitlisting users for CI on GitHub does not work > ------------------------------------------------ > > Key: OVIRT-2843 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2843 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: GitHub > Reporter: Tomas Golembiovsky > Assignee: Barak Korren > > I've tried multiple times to whitelist multiple different people in CI integration with GitHub by using the `ci add to whitelist` but it does not seem to work. IIRC it runs the tests but does not whitelist the PR originator. > By the way there's a typo in Infra documentation in the command -- the word _whitelist_ is misspelled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #300 ovirt-engine-ui-extensions [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 vm0009.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2843) Whitlisting users for CI on GitHub does not work
by Tomas Golembiovsky (oVirt JIRA) 27 Nov '19

27 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2843?page=com.atlassian.jira.… ] Tomas Golembiovsky commented on OVIRT-2843: ------------------------------------------- Btw it’s this project: [https://github.com/oVirt/v2v-conversion-host|https://github.com/oVirt/v2v-c…] > Whitlisting users for CI on GitHub does not work > ------------------------------------------------ > > Key: OVIRT-2843 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2843 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: GitHub > Reporter: Tomas Golembiovsky > Assignee: infra > > I've tried multiple times to whitelist multiple different people in CI integration with GitHub by using the `ci add to whitelist` but it does not seem to work. IIRC it runs the tests but does not whitelist the PR originator. > By the way there's a typo in Infra documentation in the command -- the word _whitelist_ is misspelled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2843) Whitlisting users for CI on GitHub does not work
by Tomas Golembiovsky (oVirt JIRA) 27 Nov '19

27 Nov '19

Tomas Golembiovsky created OVIRT-2843: ----------------------------------------- Summary: Whitlisting users for CI on GitHub does not work Key: OVIRT-2843 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2843 Project: oVirt - virtualization made easy Issue Type: Bug Components: GitHub Reporter: Tomas Golembiovsky Assignee: infra I've tried multiple times to whitelist multiple different people in CI integration with GitHub by using the `ci add to whitelist` but it does not seem to work. IIRC it runs the tests but does not whitelist the PR originator. By the way there's a typo in Infra documentation in the command -- the word _whitelist_ is misspelled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 105134, 2 (vdsm-jsonrpc-java) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #1934 ovirt-engine [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #15042 vdsm [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #15028 vdsm [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #15021 vdsm [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 vm0009.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2842) add Lucia Jelinkova to ovirt-engine frontend maintainers
by Michal Skrivanek (oVirt JIRA) 27 Nov '19

27 Nov '19

Michal Skrivanek created OVIRT-2842: --------------------------------------- Summary: add Lucia Jelinkova to ovirt-engine frontend maintainers Key: OVIRT-2842 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2842 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra following the votes in https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/6IKNDWBPSZRKZ3… please add Lucia to the list of maintainers Thanks! michal -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104778, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[CQ]: 104778, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #43 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-ovirt-master/43/ Build Name: #43 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 1

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #14991 vdsm [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #6569 ovirt-system-tests [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 openshift-integ-tests-container-tz6s7.

1 0

[JENKINS] Failed to setup proejct ovirt-engine-sdk_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #18 ovirt-engine-sdk [build-artifacts]. 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 vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 104455, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[CQ]: 104976, 3 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[CQ]: 104976, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[CQ]: 105090, 2 (vdsm-jsonrpc-java) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '19

26 Nov '19

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

1 0

[CQ]: 105081, 1 (vdsm-jsonrpc-java) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '19

26 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_gate
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #177. 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-chktw.

1 0

[CQ]: 105114, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '19

26 Nov '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 263 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '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/263/ Build Number: 263 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #263 [Ori Liel] Adapt add quota cluster limits test to API V4 [Evgheni Dereveanchin] Fix EPEL s390x mirror definition [Barak Korren] global-setup: Ensure selinux-policy is up to date ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 098_ovirt_provider_ovn.use_ovn_provider_43 Error Message: Fault reason is "Operation Failed". Fault detail is "[Cannot add a Network Interface when VM is not Down, Up or Image-Locked.]". HTTP response code is 409. -------------------- >> begin captured logging << -------------------- requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:35357 py.warnings: WARNING: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:35357 "POST /v2.0/tokens/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/networks/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/subnets/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/ports/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/098_ovirt_provider_ovn.py", line 464, in use_ovn_provider _hotplug_network_to_vm(api, VM0_NAME, NETWORK_1, IFACE_NAME) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/098_ovirt_provider_ovn.py", line 404, in _hotplug_network_to_vm id=profile.id, File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 35224, in add return self._internal_add(nic, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in _internal_add return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Cannot add a Network Interface when VM is not Down, Up or Image-Locked.]". HTTP response code is 409.\n-------------------- >> begin captured logging << --------------------\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:35357\npy.warnings: WARNING: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings\n…: DEBUG: https://192.168.201.4:35357 "POST /v2.0/tokens/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/networks/ HTTP/1.1" 201 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/subnets/ HTTP/1.1" 201 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/ports/ HTTP/1.1" 201 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None\n--------------------- >> end captured logging << ---------------------'

1 6

[CQ]: 104945, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '19

26 Nov '19

Change 104945,1 (ovirt-engine-extension-aaa-jdbc) 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/104945/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17394/

1 0

[CQ]: 105111, 2 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '19

26 Nov '19

Change 105111,2 (ovirt-system-tests) 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/105111/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17390/

1 0

oVirt infra daily report - unstable production jobs - 1021
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '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/1021//artifact/exported-… Cheers, Jenkins

1 0

[CQ]: 105111,2 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Nov '19

26 Nov '19

Change 105111,2 (ovirt-system-tests) 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/105111/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2567/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #47 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/47/ Build Name: #47 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #103
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

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

1 1

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #14965 vdsm [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 vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 105028, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '19

26 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #325 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #324 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #323 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #322 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #1894 ovirt-engine [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct pywin32-py2.7_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Nov '19

26 Nov '19

Failed to run project_setup.sh for: #6 pywin32-py2.7 [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 vm0009.workers-phx.ovirt.org.

1 0

[CQ]: c5be490 (ovirt-ansible-cluster-upgrade) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '19

26 Nov '19

Change c5be490 (ovirt-ansible-cluster-upgrade) 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://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/c5be4906b281a… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17379/

1 0