February 2019 - Infra - oVirt List Archives

[CQ]: 97627,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 08 Feb '19

08 Feb '19

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

1 0

oVirt infra daily report - unstable production jobs - 729
by jenkins＠jenkins.phx.ovirt.org 08 Feb '19

08 Feb '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/729//artifact/exported-a… Cheers, Jenkins

1 0

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

07 Feb '19

Failed to run project_setup.sh for: #2710 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 vm0093.workers-phx.ovirt.org.

1 0

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

07 Feb '19

Failed to run project_setup.sh for: #2715 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 vm0039.workers-phx.ovirt.org.

1 0

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

07 Feb '19

Failed to run project_setup.sh for: #2718 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 vm0046.workers-phx.ovirt.org.

1 0

[CQ]: 93ba412 (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 07 Feb '19

07 Feb '19

Change 93ba412 (ovirt-ansible-v2v-conversion-host) 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-v2v-conversion-host/commit/93ba4120b… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12782/

1 0

[JIRA] (OVIRT-2673) network timeouts in CI
by Greg Sheremeta (oVirt JIRA) 07 Feb '19

07 Feb '19

Greg Sheremeta created OVIRT-2673: ------------------------------------- Summary: network timeouts in CI Key: OVIRT-2673 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2673 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hi, We are seeing network timeouts in CI today. Example: https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-web-ui_sta… Total download size: 241 M Installed size: 340 M Downloading Packages: [MIRROR] ovirt-engine-nodejs-8.11.4-1.fc28.x86_64.rpm: Curl error (28): Timeout was reached for http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-fc2… [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds] [MIRROR] ovirt-engine-nodejs-modules-1.8.6-1.fc28.noarch.rpm: Curl error (28): Timeout was reached for http://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_master_build-artif… [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds] [MIRROR] ovirt-engine-yarn-1.7.0-1.fc28.noarch.rpm: Curl error (28): Timeout was reached for http://jenkins.ovirt.org/job/ovirt-engine-yarn_master_build-artifacts-fc28-… [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds] [FAILED] ovirt-engine-nodejs-8.11.4-1.fc28.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success Error: Error downloading packages: -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 07 Feb '19

07 Feb '19

Failed to run project_setup.sh for: #3483 kubevirt [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-kubevirt-org-1r14k.

1 0

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

07 Feb '19

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

1 0

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 07-02-2019 ] [ 002_bootstrap.add_direct_lun_vm0 ]
by Dafna Ron 07 Feb '19

07 Feb '19

Hi, We have a failure on ovirt-engine for test 002_bootstrap.add_direct_lun_vm0 in basic suite. CQ is reporting this patch as the first one failed (i.e root cause): https://gerrit.ovirt.org/#/c/96490/ - engine: Display all errors at once when upgrading cluster compitability level But I am also seeing that this patch was merged around the same time and my be the cause https://gerrit.ovirt.org/#/c/97604/ - core: call hotplug after a new disk is added to a VM Can you please have a look at the issue? Error: <> 2019-02-06 23:34:31,586-05 WARN [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-1) [f36d809b-4bba-4926-b997-443f70f0d7a0] Validation of action 'AddDisk' failed for user admin@internal-auth z. Reasons: VAR__ACTION__ADD,VAR__TYPE__DISK,ACTION_TYPE_FAILED_DISK_SIZE_ZERO 2019-02-06 23:34:31,587-05 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-1) [f36d809b-4bba-4926-b997-443f70f0d7a0] Lock freed to object 'EngineLock:{exclusiveLocks='', sharedLocks=' [462445ca-9622-4aa9-88aa-dedea6ebbea8=VM]'}' 2019-02-06 23:34:31,593-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [f36d809b-4bba-4926-b997-443f70f0d7a0] method: runAction, params: [AddDisk, AddDiskParamete rs:{commandId='3a9584cb-b896-488e-a858-d9c97b1e2a27', user='null', commandType='Unknown', vmId='462445ca-9622-4aa9-88aa-dedea6ebbea8'}], timeElapsed: 180ms 2019-02-06 23:34:31,597-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot add Virtual Disk. Disk's provisioned size has to be greater than 0.] 2019-02-06 23:34:31,608-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-1) [] Entered SsoRestApiAuthFilter <> Thanks, Dafna

4 6