- Infra - oVirt List Archives

[JIRA] (OVIRT-1945) Allow to keep running containers in docker_cleanup
by Barak Korren (oVirt JIRA) 03 Sep '19

03 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1945?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1945: -------------------------------- Components: docker_cleanup.py > Allow to keep running containers in docker_cleanup > -------------------------------------------------- > > Key: OVIRT-1945 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1945 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: docker_cleanup.py, oVirt CI, Standard CI (Freestyle), Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > Labels: standard-ci > > docker_cleanup.py stops all running containers before it removes the images. > We should make it optional as well as allow whitelisting containers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

URGENT - ovirt-engine master is failing for the past 9 days
by Dafna Ron 03 Sep '19

03 Sep '19

Hi, We have been failing CQ master for project ovirt-engine for the past 9 days. this was reported last week and we have not yet seen a fix for this issue. the patch reported by CQ is https://gerrit.ovirt.org/#/c/101913/10 - core: Change CPU config to secure/insecure concept logs for latest failure can be found here: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15638/artifac… Error: 2019-09-01 06:31:17,248-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-1) [174bc463-9a98-441f-ad14-4d97fefde4fa] Running command: UpdateClusterCommand internal: false. Entities affected : ID: 0407bc06-4bef-4c47-99e1-0e42f9ced996 Type: ClusterAction group EDIT_CLUSTER_CONFIGURATION with role type ADMIN 2019-09-01 06:31:17,263-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [174bc463-9a98-441f-ad14-4d97fefde4fa] EVENT_ID: CLUSTER_UPDATE_CPU_WHEN_DEPRECATED(9,029), Modified the CPU Type to Intel Haswell-noTSX Family when upgrading the Compatibility Version of Cluster test-cluster because the previous CPU Type was deprecated. 2019-09-01 06:31:17,319-04 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [18fd7817] Validation of action 'UpdateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_OS_TYPE_IS_NOT_SUPPORTED_BY_ARCHITECTURE_TYPE 2019-09-01 06:31:17,329-04 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [62694a6a] Validation of action 'UpdateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_OS_TYPE_IS_NOT_SUPPORTED_BY_ARCHITECTURE_TYPE 2019-09-01 06:31:17,334-04 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [10e41cd3] Validation of action 'UpdateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_ILLEGAL_OS_TYPE_IS_NOT_SUPPORTED_BY_ARCHITECTURE_TYPE 2019-09-01 06:31:17,345-04 WARN [org.ovirt.engine.core.bll.UpdateVmTemplateCommand] (default task-1) [26a471dd] Validation of action 'UpdateVmTemplate' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM_TEMPLATE,VMT_CANNOT_UPDATE_ILLEGAL_FIELD 2019-09-01 06:31:17,352-04 WARN [org.ovirt.engine.core.bll.UpdateVmTemplateCommand] (default task-1) [32fd89b5] Validation of action 'UpdateVmTemplate' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM_TEMPLATE,VMT_CANNOT_UPDATE_ILLEGAL_FIELD 2019-09-01 06:31:17,363-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [32fd89b5] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update compatibility version of Vm/Template: [vm-with-iface], Message: [No Message] 2019-09-01 06:31:17,371-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [32fd89b5] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update compatibility version of Vm/Template: [vm-with-iface-template], Message: [No Message] 2019-09-01 06:31:17,380-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [32fd89b5] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update compatibility version of Vm/Template: [vm0], Message: [No Message] 2019-09-01 06:31:17,388-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [32fd89b5] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update compatibility version of Vm/Template: [vm1], Message: [No Message] 2019-09-01 06:31:17,405-04 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-1) [32fd89b5] Command [id=50898f00-4956-484a-94ff-f273adc2e93e]: Compensating UPDATED_ONLY_ENTITY of org.ovirt.engine.core.common.businessentities.Cluster; snapshot: Cluster [test-cluster]. 2019-09-01 06:31:17,422-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [32fd89b5] EVENT_ID: USER_UPDATE_CLUSTER_FAILED(812), Failed to update Host cluster (User: admin@internal-authz) 2019-09-01 06:31:17,422-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-1) [32fd89b5] Lock freed to object 'EngineLock:{exclusiveLocks='[5d3b2f0f-f05f-41c6-b61a-c517704f79fd=TEMPLATE, 728f5530-4e34-4c92-beef-ca494ec104b9=TEMPLATE]', sharedLocks='[a107316a-a961-403f-adb2-d01f22f0b8f1=VM, dc3a2ad8-6019-4e00-85e5-d9fba7390d4f=VM, 6348722f-61ae-40be-a2b8-bd9d086b06dc=VM]'}' 2019-09-01 06:31:17,424-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Update of cluster compatibility version failed because there are VMs/Templates [vm-with-iface, vm-with-iface-template, vm0, vm1] with incorrect configuration. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version of the VM/Template to the cluster level you want to update the cluster to and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change.] (END)

3 6

[CQ]: 103051, 2 (ovirt-engine-nodejs-modules) 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 103051,2 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102982,4 (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 102982,4 (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/103051/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102982/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1959/

1 0

[CQ]: 103051, 2 (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 103051,2 (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/103051/2 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/4771/

1 0

[CQ]: 102983, 4 (ovirt-engine-nodejs-modules) failed "ovirt-master" 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-master" change queue including change 102983,4 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102981,2 (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 102981,2 (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/102983/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102981/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15684/

1 0

[CQ]: 102915, 21 (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 102915,21 (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/102915/21 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/4770/

1 0

[CQ]: 102915, 21 (ovirt-engine-nodejs-modules) 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 102915,21 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102982,4 (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 102982,4 (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/102915/21 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102982/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1957/

1 0

[CQ]: 102982, 4 (ovirt-engine-nodejs-modules) failed "ovirt-master" 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-master" change queue including change 102982,4 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102981,2 (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 102981,2 (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/102982/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102981/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15682/

1 0

[CQ]: 102914, 3 (ovirt-engine) failed "ovirt-master" 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-master" change queue including change 102914,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/102914/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15680/

1 0

[CQ]: 102983, 4 (ovirt-engine-nodejs-modules) 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 102983,4 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102982,4 (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 102982,4 (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/102983/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102982/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1956/

1 0

[CQ]: 102983, 4 (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 102983,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/102983/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/4769/

1 0

[CQ]: 102982, 4 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests
by oVirt Jenkins 03 Sep '19

03 Sep '19

Change 102982,4 (ovirt-engine-nodejs-modules) 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/102982/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1955/

1 0

[CQ]: 102982, 4 (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 102982,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/102982/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/4768/

1 0

[CQ]: 103029, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 03 Sep '19

03 Sep '19

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

1 0

[CQ]: 66bcd08 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 03 Sep '19

03 Sep '19

Change 66bcd08 (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/66bcd087851d4c49f0c7037d599888… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15677/

1 0

[CQ]: 102840, 2 (ovirt-engine) failed "ovirt-master" 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-master" change queue including change 102840,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/102840/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15675/

1 0

[CQ]: 102492, 6 (ovirt-engine) failed "ovirt-master" 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-master" change queue including change 102492,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/102492/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15673/

1 0

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

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

1 0

[CQ]: 102229, 11 (ovirt-engine) failed "ovirt-master" 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-master" change queue including change 102229,11 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/102229/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15670/

1 0

[CQ]: 103019, 2 (ovirt-engine) failed "ovirt-master" 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-master" change queue including change 103019,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/103019/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15667/

1 0

[CQ]: 102981, 2 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 02 Sep '19

02 Sep '19

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

1 0

[CQ]: 102939, 7 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

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

1 0

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

02 Sep '19

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

1 0

[CQ]: 102235,24 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 02 Sep '19

02 Sep '19

Change 102235,24 (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/102235/24 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15653/

1 0

[CQ]: 66bcd08 (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 02 Sep '19

02 Sep '19

Change 66bcd08 (ovirt-web-ui) 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-web-ui/commit/66bcd087851d4c49f0c7037d599888… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4766/

1 0

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

02 Sep '19

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

1 0

[JIRA] (OVIRT-2787) connecting to ci slave as developer account
by Eyal Edri (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2787?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2787: ---------------------------------- I’m not sure it's possible with the current implementation of Jenkins in KubeVirt. [~accountid:557058:f57f4f3d-a7d2-40b5-8ef1-94b6bbbf8dc7] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] ? Do you have a link to example job also that you were debugging? > connecting to ci slave as developer account > ------------------------------------------- > > Key: OVIRT-2787 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Or Shoval > Assignee: infra > > Hi Infra, > sometimes in CNV we are using CI, > and stuff fails, > it would be awesome if we can get a developer profile > that allows to connect in a restricted shell / rbash (idea by Dafna) > in order to execute commands like get pods and describe pods, > that will give hint about the problems > is it possible please ? what it involves > it can reduce lot of time and effort > thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2787) connecting to ci slave as developer account
by Or Shoval (oVirt JIRA) 02 Sep '19

02 Sep '19

Or Shoval created OVIRT-2787: -------------------------------- Summary: connecting to ci slave as developer account Key: OVIRT-2787 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Or Shoval Assignee: infra Hi Infra, sometimes in CNV we are using CI, and stuff fails, it would be awesome if we can get a developer profile that allows to connect in a restricted shell / rbash (idea by Dafna) in order to execute commands like get pods and describe pods, that will give hint about the problems is it possible please ? what it involves it can reduce lot of time and effort thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

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

02 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 102981,2 (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/102981/2 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/4764/

1 0

[JIRA] (OVIRT-2764) send email on changequeue-status_master_standard-poll-upstream-sources failure
by Ehud Yonasi (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2764?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2764: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > send email on changequeue-status_master_standard-poll-upstream-sources failure > ------------------------------------------------------------------------------ > > Key: OVIRT-2764 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2764 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: danken > Assignee: Ehud Yonasi > > OVIRT-2755 has enabled the new periodic job. I'd like to receive an email when it fails. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2764) send email on changequeue-status_master_standard-poll-upstream-sources failure
by Eyal Edri (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2764?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2764: ---------------------------------- [~accountid:5aa0f39f5a4d022884128a0f] can you verify this is done? > send email on changequeue-status_master_standard-poll-upstream-sources failure > ------------------------------------------------------------------------------ > > Key: OVIRT-2764 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2764 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: danken > Assignee: infra > > OVIRT-2755 has enabled the new periodic job. I'd like to receive an email when it fails. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more
by Eyal Edri (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2782?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2782: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Configure Jenkins to wait less and allocate more > ------------------------------------------------ > > Key: OVIRT-2782 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > By default, Jenkins is configured to wait a few seconds before allocating a new node in a hope that a node in use to be freed. We can control this setting by setting > {code:java} > hudson.slaves.NodeProvisioner.initialDelay=0 > {code} > We can also control the excessive workload threshold and force Jenkins to allocate slaves for jobs in the queue... but, because Jenkins computes the excess workload value (which decides if we need to allocate a new node) using an EMA, we set it's margins to higher values and it effectively lowers its threshold so that Jenkins will allocate nodes faster and in advance. > The recommended settings by the k8s plugin to spawn a node for every build in the queue: > {code:java} > -Dhudson.slaves.NodeProvisioner.initialDelay=0 > -Dhudson.slaves.NodeProvisioner.MARGIN=50 > -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85 > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 103009, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

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

1 0

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

02 Sep '19

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

1 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot
by Dafna Ron (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2786: ---------------------------------- I am surprised it did not comment on the bug as it usually does and it also sends a mail to the list. However, I think as we are going to work with zuul, it may not be effective to work on CQ :) > Re: fc30 packages in master snapshot > ------------------------------------ > > Key: OVIRT-2786 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Adding infra-support to open a ticket. > > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > > > Hi, > > > > How are these published? > > > > A few days ago we merged patches to add fc30 builds of otopi and > > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > > good. But we do not see them in [1]. Should we? Are they stuck > > somewhere, or there is simply nothing that publishes them these days? > > Asking the latter, because the timestamps on the few files there are > > from more than 3 months ago. > > > > Thanks and best regards, > > > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > > -- > > Didi > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot
by Dafna Ron (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2786: ---------------------------------- packages only get into tested once they pass CQ. I looked at the latest patch that that build packages and it failed CQ: patch: [https://gerrit.ovirt.org/#/c/102941/|https://gerrit.ovirt.org/#/c/102941/] job [http://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-master_change-queue-tester/15617/|http://jenkins.ovirt.org/v…] > Re: fc30 packages in master snapshot > ------------------------------------ > > Key: OVIRT-2786 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Adding infra-support to open a ticket. > > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > > > Hi, > > > > How are these published? > > > > A few days ago we merged patches to add fc30 builds of otopi and > > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > > good. But we do not see them in [1]. Should we? Are they stuck > > somewhere, or there is simply nothing that publishes them these days? > > Asking the latter, because the timestamps on the few files there are > > from more than 3 months ago. > > > > Thanks and best regards, > > > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > > -- > > Didi > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

3 2

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot
by Anton Marchukov (oVirt JIRA) 02 Sep '19

02 Sep '19

Anton Marchukov created OVIRT-2786: -------------------------------------- Summary: Re: fc30 packages in master snapshot Key: OVIRT-2786 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Adding infra-support to open a ticket. > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > Hi, > > How are these published? > > A few days ago we merged patches to add fc30 builds of otopi and > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > good. But we do not see them in [1]. Should we? Are they stuck > somewhere, or there is simply nothing that publishes them these days? > Asking the latter, because the timestamps on the few files there are > from more than 3 months ago. > > Thanks and best regards, > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > -- > Didi -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

fc30 packages in master snapshot
by Yedidyah Bar David 02 Sep '19

02 Sep '19

Hi, How are these published? A few days ago we merged patches to add fc30 builds of otopi and ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems good. But we do not see them in [1]. Should we? Are they stuck somewhere, or there is simply nothing that publishes them these days? Asking the latter, because the timestamps on the few files there are from more than 3 months ago. Thanks and best regards, [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ -- Didi

1 0

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

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

1 0

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

01 Sep '19

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

1 0

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

01 Sep '19

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

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Barak Korren (oVirt JIRA) 01 Sep '19

01 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2566 at 9/1/19 7:52 AM: ------------------------------------------------------------- Not for specific patches - but we can easily enable it for ALL patches. If we only want it for specific patches - we can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits. was (Author: bkorren(a)redhat.com) Not for specific patches - but we can enable it for ALL patches. We can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Barak Korren (oVirt JIRA) 01 Sep '19

01 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2566: ------------------------------------- Not for specific patches - but we can enable it for ALL patches. We can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

Fwd: Zuul posts non hiddable Gerrit comments
by Barak Korren 01 Sep '19

01 Sep '19

What is out current plan for upgrading to Gerrit 2.15+ ? As you can see below one of the nice features it provides, is the ability to hide auto-generated comments from the UI. This will allow use to de-clutter the comment lists on patches making them easier to track and read. ---------- Forwarded message --------- From: Vitaliy Lotorev <lotorev(a)gmail.com> Date: Fri, 30 Aug 2019 at 01:01 Subject: Zuul posts non hiddable Gerrit comments To: <zuul-discuss(a)lists.zuul-ci.org> Hi, Starting with at least v2.15 Gerrit is able to differentiate bot comments and hide them using 'Show comments' trigger on web UI. This is achived either using tagged comments or robot comments. A while ago I filed an issue about Zuul not using these technics [1] (ticket has links for Gerrit docs with tagged and robot comments). This results that Zuul comments are not hiddable in Gerrit. AFAIK, sending tagged comments via SSH to Gerrit is easy (one-line of code at [2]). I could try providing a patch for tagged comments. What Zuul maintainers think about adding support for bot comments? Should not be sending tagged comments done only if Gerrit version >= 2.15? [1] https://storyboard.openstack.org/#!/story/2005661 [2] https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/gerrit/gerritco… _______________________________________________ Zuul-discuss mailing list Zuul-discuss(a)lists.zuul-ci.org http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 179 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Sep '19

01 Sep '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/179/ Build Number: 179 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #179 [edwardh(a)redhat.com] network, ovirtlib: Expose the root system through sdkentity ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.ha_recovery_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2 lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0 lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output: 7527 lago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527 lago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0 --------------------- >> 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 "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 725, in ha_recovery lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output:\n 7527\n\nlago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527\n\nlago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0\n--------------------- >> end captured logging << ---------------------'

1 1

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

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

1 0

oVirt infra daily report - unstable production jobs - 933
by jenkins＠jenkins.phx.ovirt.org 31 Aug '19

31 Aug '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/933//artifact/exported-a… Cheers, Jenkins

1 0

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

30 Aug '19

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

1 0

[oVirt] [CQ weekly status] [30-08-2019]
by Dusan Fodor 30 Aug '19

30 Aug '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: NOT RELEVANT This CQ is not followed anymore, since it's about to be decommissioned. *CQ-4.3*: YELLOW (#1) Last failure was on 28-08 for ovirt-web-ui. It was solved soon after by change 57c5c4b. *CQ-Master:* RED (#1) Last failure was on 30-08 for ovirt-engine in host-deployment. This issue is under investigation. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt .org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

1 0

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

30 Aug '19

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

1 0