- Infra - oVirt List Archives

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 2

[CQ]: 103072, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Sep '19

06 Sep '19

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

1 0

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #8 vdsm [poll-upstream-sources]. 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-z9wp8.

1 0

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #8 vdsm [poll-upstream-sources]. 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-mmh5q.

1 0

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #8 vdsm [poll-upstream-sources]. 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-mchxp.

1 0

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

06 Sep '19

Failed to run project_setup.sh for: #5436 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-8knxs.

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

Failed to run project_setup.sh for: #5436 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-5tsf3.

1 0

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

06 Sep '19

Failed to run project_setup.sh for: #5436 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-6893k.

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

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

1 0

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

06 Sep '19

Failed to run project_setup.sh for: #5435 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-6s4gm.

1 0

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

06 Sep '19

Failed to run project_setup.sh for: #5435 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-930rz.

1 0

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

06 Sep '19

Failed to run project_setup.sh for: #5435 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-21l3s.

1 0

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

06 Sep '19

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

1 2

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-v2khm.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-58qm9.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-mt1hp.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-d2h24.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-n2l3x.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-h3qv9.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-rlb0h.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-v37ch.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 06 Sep '19

06 Sep '19

Failed to run project_setup.sh for: #347 ovirt-system-tests [poll-upstream-sources]. 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-13bnv.

1 0

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

06 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/939//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 103087, 1 (ovirt-release) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Sep '19

06 Sep '19

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

1 0

[CQ]: 103086,1 (ovirt-release) failed "ovirt-4.3" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

Change 103086,1 (ovirt-release) 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/103086/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2019/

1 0

[CQ]: 102639,10 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

Change 102639,10 (vdsm) 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/102639/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15732/

1 0

[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue
by Nir Soffer (oVirt JIRA) 05 Sep '19

05 Sep '19

Nir Soffer created OVIRT-2794: --------------------------------- Summary: OST is broken since this morning - looks like infra issue Key: OVIRT-2794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra The last successful build was today at 08:10: Since then all builds fail very early with the error below - which is not related to oVirt. Removing image: sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa, force=True Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222, in _raise_for_status response.raise_for_status() File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True&noprune=False During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 349, in <module> main() File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 37, in main safe_image_cleanup(client, whitelisted_repos) File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 107, in safe_image_cleanup _safe_rm(client, parent) File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 329, in _safe_rm client.images.remove(image_id, force=force) File "/usr/lib/python3.6/site-packages/docker/models/images.py", line 288, in remove self.client.api.remove_image(*args, **kwargs) File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line 19, in wrapped return f(self, resource_id, *args, **kwargs) File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in remove_image return self._result(res, True) File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228, in _result self._raise_for_status(response) File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224, in _raise_for_status raise create_api_error_from_http_exception(e) File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception raise cls(e, response=response, explanation=explanation) docker.errors.NotFound: 404 Client Error: Not Found ("reference does not exist") Aborting. Build step 'Execute shell' marked build as failure x [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5542/console> #5542 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5542/> Sep 5, 2019 3:02 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5542/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5541/console> #5541 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5541/> Sep 5, 2019 3:02 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5541/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5540/console> #5540 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5540/> Sep 5, 2019 3:01 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5540/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5539/console> #5539 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5539/> Sep 5, 2019 2:13 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5539/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5538/console> #5538 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5538/> Sep 5, 2019 1:58 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5538/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5537/console> #5537 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5537/> Sep 5, 2019 1:50 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5537/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5536/console> #5536 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5536/> Sep 5, 2019 10:21 AM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5536/> [image: x] <http://jenkins.ovirt.org/job/ovirt-system-tests_manual/jobConfigHistory/sho…> [image: Success > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5535/console> #5535 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5535/> Sep 5, 2019 8:10 AM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5535/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[CQ]: 79a3ea7 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

Change 79a3ea7 (ovirt-web-ui) 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-web-ui/commit/79a3ea7681c4c29f8329706d8c7528… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15731/

1 0

[CQ]: 103075,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

Change 103075,1 (vdsm) 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/103075/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2014/

1 0

[JIRA] (OVIRT-2793) ansiblize resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 05 Sep '19

05 Sep '19

Evgheni Dereveanchin created OVIRT-2793: ------------------------------------------- Summary: ansiblize resources.ovirt.org Key: OVIRT-2793 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2793 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra The resources.ovirt.org file server is currently managed by puppet with bits of undocumented stuff scattered around the place. Logging a ticket to document stuff that's currently present on Resources to see how we can move that to Ansible and re-use existing OSAS roles where possible. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

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

05 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 79a3ea7 (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/79a3ea7681c4c29f8329706d8c7528… 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/4788/

1 0

[JIRA] (OVIRT-2791) mirrors.phx returns 404 when accessing metadata
by Dusan Fodor (oVirt JIRA) 05 Sep '19

05 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2791?page=com.atlassian.jira.… ] Dusan Fodor updated OVIRT-2791: ------------------------------- Resolution: Fixed Status: Done (was: To Do) The patch [1] indeed helped with the issue, this is resolved now. > mirrors.phx returns 404 when accessing metadata > ----------------------------------------------- > > Key: OVIRT-2791 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2791 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > > http://mirrors.phx.ovirt.org/repos/yum/epel-el7/2019-05-09-04-45/repodata/5…: [Errno 14] HTTP Error 404 - Not Found > Job example that failed on this: > http://jenkins.ovirt.org/job/ovirt-system-tests_manual/5532/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2792) Error running global_setup.sh with metrics suite
by Evgeny Slutsky (oVirt JIRA) 05 Sep '19

05 Sep '19

Evgeny Slutsky created OVIRT-2792: ------------------------------------- Summary: Error running global_setup.sh with metrics suite Key: OVIRT-2792 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2792 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Evgeny Slutsky Assignee: infra when trying to run the suit manually in jenkin, this error received: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[CQ]: 4d92421 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '19

05 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 4d92421 (ovirt-ansible-cluster-upgrade) failed. However, this change seems not to be the root cause for this failure. Change 7aa8be7 (ovirt-ansible-cluster-upgrade) 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 7aa8be7 (ovirt-ansible-cluster- upgrade) 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-cluster-upgrade/commit/4d92421a8cf4c… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/7aa8be7a74fbf… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4786/

1 0

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

05 Sep '19

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

1 0

[CQ]: 7aa8be7 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

Change 7aa8be7 (ovirt-ansible-cluster-upgrade) 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-cluster-upgrade/commit/7aa8be7a74fbf… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4784/

1 0

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

05 Sep '19

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

1 0

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

05 Sep '19

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

1 0

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

05 Sep '19

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

1 0

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

05 Sep '19

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

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5432 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-4b9js.

1 0

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

05 Sep '19

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

1 0