September 2019 - Infra - oVirt List Archives

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #709 vdsm [check-network]. 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-jr4rr.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #709 vdsm [check-network]. 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-z5br9.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #706 vdsm [check-network]. 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-wfgsh.

1 4

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

11 Sep '19

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

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #612 kubernetes-nmstate [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-pls56.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #612 kubernetes-nmstate [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-hp197.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #611 kubernetes-nmstate [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-17z41.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #611 kubernetes-nmstate [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-v9zqg.

1 0

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

11 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 103235,4 (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/103235/4 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/4801/

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

Failed to run project_setup.sh for: #610 kubernetes-nmstate [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-j2bb0.

1 0