February 2019 - Infra - oVirt List Archives

what is a telecommunications job
by kumarfield28＠gmail.com 23 Sep '19

23 Sep '19

These days, you will often come across telecommunication field technician jobs on the internet and newspapers. This must have gotten you curious regarding telecom engineer jobs. You might be wondering whether it would be the right career option for you and what kind of telecom services you will need to provide if this is the field you opt for. If that is the case, this is where your search culminates since we will provide you with the required details regarding telecom engineer jobs and services among other things. https://www.fieldengineer.com/blogs/telecom-engineer-job-description/

3 2

[oVirt CI] standard-enqueue - Build #17451 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jul '19

24 Jul '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/17451/ Build Name: #17451 Build Description: Gerrit: 95261 - ovirt-vmconsole (4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/95261 - title: build: Fix build broken on Fedora - project: ovirt-vmconsole - branch: master - author: Tomasz Baranski <tbaransk(a)redhat.com>

2 1

Re: INVALID_SERVICE: ovirtlago
by Barak Korren 18 Mar '19

18 Mar '19

That is not the real issue, the real issue seems to be this: + sudo -n systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. + sudo -n systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2019-02-25 04:03:52 UTC; 45ms ago Docs: https://docs.docker.com Process: 15496 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 15496 (code=exited, status=1/FAILURE) Feb 25 04:03:52 openshift-integ-tests-container-6bmr3 systemd[1]: Failed to start Docker Application Container Engine. Feb 25 04:03:52 openshift-integ-tests-container-6bmr3 systemd[1]: Unit docker.service entered failed state. Feb 25 04:03:52 openshift-integ-tests-container-6bmr3 systemd[1]: docker.service failed. + : + log ERROR 'Failed to start docker service' + local level=ERROR So docker is failing to start in the integ-test container. Here is the podspec that was used: ---apiVersion: v1kind: Podmetadata: generateName: jenkins-slave labels: integ-tests-container: "" namespace: jenkins-ovirt-orgspec: containers: - env: - name: JENKINS_AGENT_WORKDIR value: /home/jenkins - name: CI_RUNTIME_UNAME value: jenkins - name: STDCI_SLAVE_CONTAINER_NAME value: im_a_container - name: CONTAINER_SLOTS value: /var/lib/stdci image: docker.io/ovirtinfra/el7-runner-node:12c9f471a6e9eccd6d5052c6c4964fff3b6670c9 command: ['/usr/sbin/init'] livenessProbe: exec: command: ['systemctl', 'status', 'multi-user.target'] initialDelaySeconds: 360 periodSeconds: 7200 name: jnlp resources: limits: memory: 32Gi requests: memory: 32Gi securityContext: privileged: true volumeMounts: - mountPath: /var/lib/stdci name: slave-cache - mountPath: /dev/shm name: dshm workingDir: /home/jenkins tty: true nodeSelector: model: r620 serviceAccount: jenkins-slave volumes: - hostPath: path: /var/lib/stdci type: DirectoryOrCreate name: slave-cache - emptyDir: medium: Memory name: dshm Adding Gal and infra list. On Mon, 25 Feb 2019 at 08:45, Eitan Raviv <eraviv(a)redhat.com> wrote: > Hi, > I have some OST patches failing on: > > *04:03:53* Error: INVALID_SERVICE: ovirtlago > > e.g. https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/3443/… > > I am fully rebased on ost master. > > Can you have a look? > > Thank you > > > ---------- Forwarded message --------- > From: Galit Rosenthal <grosenth(a)redhat.com> > Date: Mon, Feb 25, 2019 at 8:35 AM > Subject: Re: INVALID_SERVICE: ovirtlago > To: Eitan Raviv <eraviv(a)redhat.com> > > > I think you should consult Barak > > On Sun, Feb 24, 2019 at 8:26 PM Eitan Raviv <eraviv(a)redhat.com> wrote: > >> *13:58:57* ++ sudo -n firewall-cmd --query-service=ovirtlago*13:58:58* Error: INVALID_SERVICE: ovirtlago >> >> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/3430/… >> >> > > -- > > GALIT ROSENTHAL > > SOFTWARE ENGINEER > > Red Hat > > <https://www.redhat.com/> > > galit(a)gmail.com T: 972-9-7692230 > <https://red.ht/sig> > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

4 9

[ OST Failure Report ] [ oVirt Master (ovirt-engine-nodejs-modules) ] [ 27-02-2019 ] [ 002_bootstrap.add_vm2_lease ]
by Dafna Ron 10 Mar '19

10 Mar '19

Hi, We have a failure on the project in basic suite, master branch. The recent failure was in patch: https://gerrit.ovirt.org/#/c/98087/1 - Add pre-seed for ovirt-web-ui CQ is pointing at the below as the root cause (which was merged a while back): https://gerrit.ovirt.org/#/c/97491/ - Add pre-seed for ovirt-web-ui Can you please check the issue as it seems both patches are changing the same thing and the project seem to be broken since https://gerrit.ovirt.org/#/c/97491/3 Latest failure: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/ Logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/artifa… errors from logs: Engine: 2019-02-27 13:37:28,479-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [74283e25] Transaction rolled-back for command 'org.ovirt.engine.core.bll.UpdateVmCommand'. 2019-02-27 13:37:28,483-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [74283e25] EVENT_ID: USER_FAILED_UPDATE_VM(58), Failed to update VM vm2 (User: admin@inter nal-authz). 2019-02-27 13:37:28,485-05 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [74283e25] Lock freed to object 'EngineLock:{exclusiveLocks='[vm2=VM_NAME]', sharedLocks='[3500eb82-e5e2-4e24-b41c-ea 02d9f6adee=VM]'}' 2019-02-27 13:37:28,485-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [74283e25] method: runAction, params: [UpdateVm, VmManagementParametersBase:{commandId='340 59769-05b9-429e-8356-f6b9b9953f55', user='admin', commandType='UpdateVm', vmId='3500eb82-e5e2-4e24-b41c-ea02d9f6adee'}], timeElapsed: 6618ms 2019-02-27 13:37:28,486-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [] 2019-02-27 13:37:28,579-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] method: get, params: [e29c0ba1-464c-4eb4-a8f2-c6933d9 9969a], timeElapsed: 3ms vdsm: 2019-02-27 13:37:21,987-0500 INFO (jsonrpc/1) [vdsm.api] FINISH lease_info error=No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee from=::ffff:192.168.201.4,43920, flow_id=117dec74-ad59-4b12-8148-b2c130337c10, task_id=9c297d41-0aa7-4c74-b268-b710e666bc6c (api:52) 2019-02-27 13:37:21,988-0500 ERROR (jsonrpc/1) [storage.TaskManager.Task] (Task='9c297d41-0aa7-4c74-b268-b710e666bc6c') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in lease_info File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 3702, in lease_info info = dom.lease_info(lease.lease_id) File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 674, in lease_info return vol.lookup(lease_id) File "/usr/lib/python2.7/site-packages/vdsm/storage/xlease.py", line 553, in lookup raise NoSuchLease(lease_id) NoSuchLease: No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee 2019-02-27 13:37:21,988-0500 INFO (jsonrpc/1) [storage.TaskManager.Task] (Task='9c297d41-0aa7-4c74-b268-b710e666bc6c') aborting: Task is aborted: u'No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee' - code 100 (task:1181) 2019-02-27 13:37:21,988-0500 ERROR (jsonrpc/1) [storage.Dispatcher] FINISH lease_info error=No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee (dispatcher:87) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line 74, in wrapper result = ctask.prepare(func, *args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in wrapper return m(self, *a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1189, in prepare raise self.error NoSuchLease: No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee

5 9

[JIRA] (OVIRT-2566) make network suite blocking
by danken (oVirt JIRA) 04 Mar '19

04 Mar '19

danken created OVIRT-2566: ----------------------------- Summary: 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#100095)

2 1

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 496 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/496/ Build Number: 496 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #496 [Sandro Bonazzola] repos: master: switch to gluster 5 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.resize_and_refresh_storage_domain_42 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: end task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: Running 59628f54 on lago-compat-4-2-suite-master-engine: lvresize --size +3000M /dev/mapper/vg1_storage-lun0_bdev lago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine returned with 0 lago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine output: Size of logical volume vg1_storage/lun0_bdev changed from 20.00 GiB (5120 extents) to <22.93 GiB (5870 extents). Logical volume vg1_storage/lun0_bdev successfully resized. lago.ssh: DEBUG: start task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: end task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: Running 59c76e60 on lago-compat-4-2-suite-master-engine: cat /root/multipath.txt lago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine returned with 0 lago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine output: 360014052b36c080242849af94e08d593 3600140577ca2fe2129b46cfadb969690 3600140582c361006901472d903755e3c 36001405e4f3abc5714e4d42929c9534b 36001405ec963d2b05d748c4bb4ba46f6 --------------------- >> 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.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 527, in resize_and_refresh_storage_domain logical_units=luns File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__ self.gen.throw(type, value, traceback) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/__init__.py", line 264, in TestEvent 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:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: end task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: Running 59628f54 on lago-compat-4-2-suite-master-engine: lvresize --size +3000M /dev/mapper/vg1_storage-lun0_bdev\nlago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine returned with 0\nlago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine output:\n Size of logical volume vg1_storage/lun0_bdev changed from 20.00 GiB (5120 extents) to <22.93 GiB (5870 extents).\n Logical volume vg1_storage/lun0_bdev successfully resized.\n\nlago.ssh: DEBUG: start task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: end task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: Running 59c76e60 on lago-compat-4-2-suite-master-engine: cat /root/multipath.txt\nlago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine returned with 0\nlago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine output:\n 360014052b36c080242849af94e08d593\n3600140577ca2fe2129b46cfadb969690\n3600140582c361006901472d903755e3c\n36001405e4f3abc5714e4d42929c9534b\n36001405ec963d2b05d748c4bb4ba46f6\n\n--------------------- >> end captured logging << ---------------------'

1 3

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 498 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/498/ Build Number: 498 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #498 [Milan Zamazal] Add upgrade-from-release_suite-4.3 [Gal Ben Haim] global-setup: Collect more info about docker [Barak Korren] slaves_deploy: Fix STDCI slave settings ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.get_host_devices_41 Error Message: Could not find block_vda_1 device in host devices: Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py", line 1016, in get_host_devices raise RuntimeError('Could not find block_vda_1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda_1 device in host devices:

1 1

[CQ]: 98126,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 01 Mar '19

01 Mar '19

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

1 0

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

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

1 0

[CQ]: 98058, 4 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1437 containerized-data-importer [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-7gf81.

1 1

[CQ]: 96485,6 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

Change 96485,6 (ovirt-imageio) 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/96485/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13187/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1437 containerized-data-importer [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-srt89.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1436 containerized-data-importer [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-p1nn5.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1435 containerized-data-importer [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-thpcq.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1433 containerized-data-importer [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-hkn5s.

1 1

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1432 containerized-data-importer [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-x502z.

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-02-2019 ] [ 002_bootstrap.resize_and_refresh_storage_domain ]
by Dafna Ron 28 Feb '19

28 Feb '19

Hi, The test failed due to not finding master storage domain I am seeing a build of engine that passed so its possible that this is related to the random failures we have been having on other tests but since the change reported is storage related, can you please review the logs to see if anything happened to the master domain while trying to resize? CQ reported this change as root cause: https://gerrit.ovirt.org/#/c/98015/6 - blockSD: Move legacy block size constants to sd build failure: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13175/ logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13175/artifa… errors in log: 2019-02-27 17:35:02,222-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM la go-basic-suite-master-host-1 command ConnectStoragePoolVDS failed: Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5a9' 2019-02-27 17:35:02,222-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker. ConnectStoragePoolVDSCommand' return value 'StatusOnlyReturn [status=Status [code=304, message=Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5 a9']]' 2019-02-27 17:35:02,222-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] HostName = lago-basic-suite-master-host-1 2019-02-27 17:35:02,223-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] Command 'ConnectStoragePoolVDSCommand(HostName = lago-basic-suite-master-host-1, ConnectStoragePoolVDSCommandParameters:{hostId='1ac0eda2-0980-40df-b029-b262680696a4', vdsId='1ac0eda2-0980-40df-b029-b262680696a4', storagePoolId='1c79b83e-32d6-43e0-bc61-2955e42c3a58', masterVersion='1'})' execution failed: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5a9' 2019-02-27 17:35:02,223-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] Exception: org.ovirt.engine.core.vdsbroker.irsbroker.IRSNoMasterDomainException: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5a9' at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:50) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand.proceedConnectProxyReturnValue(ConnectStoragePoolVDSCommand.java:48) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand.proceedProxyReturnValue(ConnectStoragePoolVDSCommand.java:36) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand.executeVdsBrokerCommand(ConnectStoragePoolVDSCommand.java:32) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:396) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source) [:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_191] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) [:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_191] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.bll.storage.pool.RefreshPoolSingleAsyncOperation.execute(RefreshPoolSingleAsyncOperation.java:59) [bll.jar:] at org.ovirt.engine.core.utils.SynchronizeNumberOfAsyncOperations$AsyncOpThread.call(SynchronizeNumberOfAsyncOperations.java:43) [utils.jar:] at org.ovirt.engine.core.utils.SynchronizeNumberOfAsyncOperations$AsyncOpThread.call(SynchronizeNumberOfAsyncOperations.java:32) [utils.jar:] at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalCallable.call(ThreadPoolUtil.java:117) [utils.jar:] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_191] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:]

2 2

[CQ]: 98063, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

Change 98063,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/98063/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13180/

1 0

[ANN] oVirt 4.3.1 is now generally available
by Sandro Bonazzola 28 Feb '19

28 Feb '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.1, as of February 26th, 2019. This update is the first in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available for EL7 only - oVirt Node is available for EL7 only [2] - Fedora 28 based appliance and node couldn't be built due to a bug in Lorax (the tool used to build the images) affecting Fedora 28 and still pending a build from Fedora project. oVirt Node has been updated including: - oVirt 4.3.1: http://www.ovirt.org/release/4.3.1/ - ansible-2.7.8: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… Relevant EPEL Errata included: - FEDORA-EPEL-2019-5f2f93029f security update in Fedora EPEL 7 for ansible ( https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5f2f93029f ) Relevant CentOS Errata included: - CESA-2019:0231 Important CentOS 7 spice Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-February/023192.html ) - CESA-2019:0368 Important CentOS 7 systemd Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-February/023202.html ) Additional Resources: * Read more about the oVirt 4.3.1 release highlights: http://www.ovirt.org/release/4.3.1/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.1/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

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

28 Feb '19

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

1 0

[CQ]: 98099, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Feb '19

28 Feb '19

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

1 0

[CQ]: 98096,1 (ovirt-release) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

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

1 0

[CQ]: 98098,1 (ovirt-appliance) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

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

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Anton Marchukov (oVirt JIRA) 28 Feb '19

28 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2688: ---------------------------------------- Most of 4.3 suites are already prepared, we are making sure they are working and then we will enable 4.3 selector. -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Eyal Edri (oVirt JIRA) 28 Feb '19

28 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2688: ---------------------------------- Its also pending when/if the 4.3 suites are ready and working, I think they are still WIP. On Thu, Feb 28, 2019 at 9:50 AM Yedidyah Bar David <didi(a)redhat.com> wrote: > On Wed, Feb 27, 2019 at 9:56 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > When starting manual OST job, we can select engine version. > > The available options are: > > - master > > - 42 > > > > Since we have now 4.3 branch, we should be able to select 4.3 engine. > > We didn't branch yet. Tal should branch it RSN. > -- > Didi > _______________________________________________ > 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/2R7NEKEVL3MEV… > -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

2 1

OST manual: enable engine 4.3
by Nir Soffer 28 Feb '19

28 Feb '19

When starting manual OST job, we can select engine version. The available options are: - master - 42 Since we have now 4.3 branch, we should be able to select 4.3 engine. See attached screenshot.

3 2

How to run manual job with standard STDCIV2 build results?
by Yedidyah Bar David 28 Feb '19

28 Feb '19

Hi all, I run [1] and it fails with [2]: 2019-02-27 08:27:00,821::log_utils.py::__enter__::600::ovirtlago.reposetup::INFO:: # Running repoman: [0m [0m 2019-02-27 08:27:00,822::log_utils.py::__enter__::600::lago.utils::DEBUG::start task:87982007-be04-4d4b-af19-751f85f8df25:Run command: "repoman" "--option=main.on_empty_source=warn" "--option=store.RPMStore.on_wrong_distro=copy_to_all" "--option=store.RPMStore.with_srcrpms=false" "--option=store.RPMStore.with_sources=false" "--option=store.RPMStore.rpm_dir=" "/dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default" "add" "conf:/home/jenkins/workspace/ovirt-system-tests_manual/ovirt-system-tests/upgrade-from-release-suite-master/extra_sources" "/var/lib/lago/ovirt-master-tested-el7:only-missing" "/var/lib/lago/ovirt-master-snapshot-static-el7:only-missing" "/var/lib/lago/glusterfs-5-el7:only-missing" "/var/lib/lago/centos-updates-el7:only-missing" "/var/lib/lago/centos-base-el7:only-missing" "/var/lib/lago/centos-extras-el7:only-missing" "/var/lib/lago/epel-el7:only-missing" "/var/lib/lago/centos-ovirt-4.3-el7:only-missing" "/var/lib/lago/centos-ovirt-common-el7:only-missing" "/var/lib/lago/centos-qemu-ev-testing-el7:only-missing" "/var/lib/lago/centos-opstools-testing-el7:only-missing" "/var/lib/lago/centos-sclo-rh-release-el7:only-missing": 2019-02-27 08:28:08,161::utils.py::_run_command::192::lago.utils::DEBUG::87982007-be04-4d4b-af19-751f85f8df25: command exit with return code: 1 2019-02-27 08:28:08,161::utils.py::_run_command::197::lago.utils::DEBUG::87982007-be04-4d4b-af19-751f85f8df25: command stderr: 2019-02-27 08:27:01,014::INFO::repoman.cmd:: 2019-02-27 08:27:01,014::INFO::repoman.cmd::Adding artifacts to the repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default 2019-02-27 08:27:01,015::INFO::repoman.common.stores.RPM::Loading repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default 2019-02-27 08:27:01,015::INFO::repoman.common.stores.RPM::Repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default loaded 2019-02-27 08:27:01,015::INFO::repoman.common.stores.iso::Loading repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default 2019-02-27 08:27:01,016::INFO::repoman.common.stores.iso::Repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default loaded 2019-02-27 08:27:01,020::INFO::repoman.common.repo::Resolving artifact source rec:https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/a… 2019-02-27 08:27:01,022::INFO::repoman.common.sources.url::Recursively fetching URL (level 0): https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/artif… 2019-02-27 08:28:08,127::ERROR::repoman.cmd::maximum recursion depth exceeded in cmp Perhaps this is a bug, or a result of supplying in CUSTOM_REPOS [3]: rec:https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/a… Is this a bug? If not, what's the correct way to supply a subtree of the exported artifacts of some (standard CI) build? Thanks, [1] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… [2] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… [3] https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/artif… -- Didi

3 4

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

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

1 0

[CQ]: 98015,6 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Nir Soffer (oVirt JIRA) 27 Feb '19

27 Feb '19

Nir Soffer created OVIRT-2688: --------------------------------- Summary: OST manual: enable engine 4.3 Key: OVIRT-2688 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra When starting manual OST job, we can select engine version. The available options are: - master - 42 Since we have now 4.3 branch, we should be able to select 4.3 engine. See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 98087, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[CQ]: 97485, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1423 containerized-data-importer [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-6qcbv.

1 0

[CQ]: 97485,9 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 97485,9 (ovirt-provider-ovn) 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://gerrit.ovirt.org/#/c/97485/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3953/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1421 containerized-data-importer [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-lxhwg.

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

Tracking creation of 4.3 branch
by Dafna Ron 27 Feb '19

27 Feb '19

Hi, I created a google sheet so we can track which projects created the 4.3 branch and also which ones have already added the branch to 4.3 CQ in CI [1] Can everyone please go through the sheet and mark the progress there + assign a contact for the project for doing this work? [1] https://docs.google.com/spreadsheets/d/1i142cTN_0QwOvogtlQiF6bcIYxTpBqYBed2… thanks! Dafna

2 4

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1416 containerized-data-importer [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-75vnn.

1 3

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

2 2

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2687: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2687: ---------------------------------- thanks. we can close this as I can see the patch managed to trigger the build after adding to list; https://gerrit.ovirt.org/#/c/92805/ > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Eyal Edri (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2687: ---------------------------------- merged On Wed, Feb 27, 2019, 12:48 Dafna Ron (oVirt JIRA) < > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2687: ---------------------------------- patch added - https://gerrit.ovirt.org/#/c/98083/ > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

2 1

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Ondra Machacek (oVirt JIRA) 27 Feb '19

27 Feb '19

Ondra Machacek created OVIRT-2687: ------------------------------------- Summary: Please add Carlos Rodrigues to CI whitelist Key: OVIRT-2687 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ondra Machacek Assignee: infra Hi, please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. Thanks, Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2686) CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2686?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2686: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error > --------------------------------------------------------------------------- > > Key: OVIRT-2686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2686 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Galit Rosenthal > Assignee: Evgheni Dereveanchin > > For example: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2686) CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error
by Galit Rosenthal (oVirt JIRA) 27 Feb '19

27 Feb '19

Galit Rosenthal created OVIRT-2686: -------------------------------------- Summary: CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error Key: OVIRT-2686 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2686 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Galit Rosenthal Assignee: infra For example: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97841,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

4 5

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1414 containerized-data-importer [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-frslf.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1414 containerized-data-importer [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-dn8sg.

1 0

Space problem on mail server
by Marc Dequènes (Duck) 27 Feb '19

27 Feb '19

Quack, I'm just back from event and vacation and I barely scratched the top of my inbox but I saw postmaster 26 messages about lack of space. I'm taking care of it now and will need to shutdown the VM a short time to rework storage and partitioning. We have a MX2 so it should only create a small delay to receive ML messages. \_o<

2 2

[CQ]: 97976,19 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

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

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

1 0

[CQ]: 97976,19 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 Feb '19

26 Feb '19

Failed to run project_setup.sh for: #1405 containerized-data-importer [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-cb7nh.

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

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

1 0

[CQ]: 98026,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

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

1 0

[JIRA] (OVIRT-2685) Email not found on mailing list
by Bitbucket (oVirt JIRA) 26 Feb '19

26 Feb '19

Bitbucket created OVIRT-2685: -------------------------------- Summary: Email not found on mailing list Key: OVIRT-2685 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2685 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Bitbucket Assignee: infra Hi, I'm trying to do a password reset on mailling list, it says email is not found. I'm receiving mailing list daily on al(a)cyberversion.com -- Robin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 Feb '19

26 Feb '19

Failed to run project_setup.sh for: #1403 containerized-data-importer [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-lpdpc.

1 0

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

26 Feb '19

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

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Anton Marchukov closed OVIRT-2662. ---------------------------------- Makes sense. Closing > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > 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

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2658: ----------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2502) official releases not being tested by change queue
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2502?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2502: -------------------------------------- Assignee: Dafna Ron (was: infra) > official releases not being tested by change queue > -------------------------------------------------- > > Key: OVIRT-2502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2502 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Dafna Ron > > Hi, > just noticed in > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… > that both the patch including the official release patch and the > post-release patch has been added to the same change queue job, causing the > official release to be skipped in favor of the post release: > - Started by upstream project ovirt-4.2_change-queue > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/> build number 8642 > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/8642/> > originally caused by: > - Started by upstream project standard-enqueue > <https://jenkins.ovirt.org/job/standard-enqueue/> build number 16477 > <https://jenkins.ovirt.org/job/standard-enqueue/16477/> > originally caused by: > - Triggered by Gerrit: https://gerrit.ovirt.org/94367 > Other triggered builds for this event. > ovirt-engine_4.2_build-artifacts-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/> > #828 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/8…> > ovirt-engine_4.2_check-merged-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/> > #800 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/800/> > - Started by upstream project ovirt-4.2_change-queue > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/> build number 8643 > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/8643/> > originally caused by: > - Started by upstream project standard-enqueue > <https://jenkins.ovirt.org/job/standard-enqueue/> build number 16478 > <https://jenkins.ovirt.org/job/standard-enqueue/16478/> > originally caused by: > - Triggered by Gerrit: https://gerrit.ovirt.org/94368 > Other triggered builds for this event. > ovirt-engine_4.2_build-artifacts-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/> > #829 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/8…> > ovirt-engine_4.2_check-merged-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/> > #801 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/801/> > This is really bad, meaning that a regression introduced in the release > patch may be completely ignored provided that the post release patch fixes > it. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> > <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Shirly Radco (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-2658: ------------------------------------- On Tue, Feb 26, 2019, 14:14 Anton Marchukov (oVirt JIRA) < Yes > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2662: ---------------------------------- I think it can be closed. The bot also mentioned that a user can be added to the oVirt org or the project if we want to add him permenantly for whitelisting. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > 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

[JIRA] (OVIRT-2625) lists.ovirt.org not showing threads
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2625?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2625: -------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > lists.ovirt.org not showing threads > ----------------------------------- > > Key: OVIRT-2625 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2625 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Marc Dequènes (Duck) > Attachments: Selection_258.png > > > Hi, > lists.ovirt.org hyperkitty is once again not showing threads. I tried to > find my old Jira ticket, but Jira is down. > For example, this doesn't show the thread, but there are 8 replies: > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SDDH2OC5RBOVYY… > Screenshot: https://imgur.com/a/xHKDN6K > [image: Selection_258.png] > -- > 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

[JIRA] (OVIRT-2639) Add support to upstream sources to be able to test github PR
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2639?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2639: -------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support to upstream sources to be able to test github PR > ------------------------------------------------------------ > > Key: OVIRT-2639 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2639 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: Daniel Belenky > > Hi, > I added to ovirt-engine-metrics a github repo as upstream source. > I would like to be able to test github PR with in jenkins. > Best regards, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2652) Supporting comments on ovirt-site Blog section
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2652?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2652: -------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Supporting comments on ovirt-site Blog section > ---------------------------------------------- > > Key: OVIRT-2652 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2652 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: Marc Dequènes (Duck) > > It would be very useful to have a comment section on our ovirt site. > It is quite standard to have that on every blog out there, and for a reason > - you get > feedback and conversation around the topic, without going somewhere else > (users list, irc, etc...) > What do we need to do to help the middle man with that? > Regards, > Roy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2658: ---------------------------------------- [~sradco(a)redhat.com] this looks to be temporary issues and I see the job is passing now. Are you ok with closing this? > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2662: ---------------------------------------- [~bkorren(a)redhat.com] are you currently handling it or somebody else have to? I see this is in progress but no owner. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > 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

[JIRA] (OVIRT-2680) puppetdb on foreman.ovirt.org OOM
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2680?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2680: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > puppetdb on foreman.ovirt.org OOM > --------------------------------- > > Key: OVIRT-2680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2680 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Emil Natan > Assignee: Evgheni Dereveanchin > > Pupperdb on forman.ovirt.org went down, it seems because of OOM. Below is the message from puppetdb-daemon.log. Not sure if this is the first time this happens, if yes then maybe just increase memory and swap. > java.lang.OutOfMemoryError: Java heap space > Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ... > Heap dump file created [285263302 bytes in 2.953 secs] > # > # java.lang.OutOfMemoryError: Java heap space > # -XX:OnOutOfMemoryError="kill -9 %p" > # Executing /bin/sh -c "kill -9 6929"... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2684) Fwd: Access to resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2684?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2684: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Fwd: Access to resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2684 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2684 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a ticket. > > Begin forwarded message: > > > > From: Gal Zaidman <gzaidman(a)redhat.com> > > Subject: Access to resources.ovirt.org > > Date: 26 February 2019 at 10:59:40 CET > > To: Anton Marchukov <amarchuk(a)redhat.com> > > > > Hi Anton, > > > > I need to get access to ssh resources.ovirt.org <http://resources.ovirt.org/>, > > I understood from Sandro that I need a ssh key for that, > > > > can you grant me access? > > > > Thanks, > > Gal Zaidman > -- > Anton Marchukov > Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2684) Fwd: Access to resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

Anton Marchukov created OVIRT-2684: -------------------------------------- Summary: Fwd: Access to resources.ovirt.org Key: OVIRT-2684 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2684 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Adding infra-support to open a ticket. > Begin forwarded message: > > From: Gal Zaidman <gzaidman(a)redhat.com> > Subject: Access to resources.ovirt.org > Date: 26 February 2019 at 10:59:40 CET > To: Anton Marchukov <amarchuk(a)redhat.com> > > Hi Anton, > > I need to get access to ssh resources.ovirt.org <http://resources.ovirt.org/>, > I understood from Sandro that I need a ssh key for that, > > can you grant me access? > > Thanks, > Gal Zaidman -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 4604050 (ovirt-ansible-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

Change 4604050 (ovirt-ansible-engine-setup) 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-engine-setup/commit/4604050e3aa8b3ba… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13137/

1 0

[CQ]: 4604050 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

Change 4604050 (ovirt-ansible-engine-setup) 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-engine-setup/commit/4604050e3aa8b3ba… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3946/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 Feb '19

26 Feb '19

Failed to run project_setup.sh for: #1400 containerized-data-importer [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-3pjd9.

1 0

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

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

1 0

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

25 Feb '19

Failed to run project_setup.sh for: #3190 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 kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 25 Feb '19

25 Feb '19

Failed to run project_setup.sh for: #1395 containerized-data-importer [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-vwskt.

1 0

[CQ]: 97398, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 25 Feb '19

25 Feb '19

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

1 0

[JIRA] (OVIRT-2682) Add Pavel Bar to CI white-list
by Evgheni Dereveanchin (oVirt JIRA) 25 Feb '19

25 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2682?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2682: ---------------------------------------- Resolution: Done Status: Done (was: To Do) The change was merged, closing the corresponding ticket. > Add Pavel Bar to CI white-list > ------------------------------ > > Key: OVIRT-2682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Fred Rolland > Assignee: infra > > https://gerrit.ovirt.org/#/c/97869/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

25 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 25 Feb '19

25 Feb '19

Failed to run project_setup.sh for: #1392 containerized-data-importer [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-bbjp8.

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 25 Feb '19

25 Feb '19

Failed to run project_setup.sh for: #252 ovirt-provider-ovn [check-merged]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0099.workers-phx.ovirt.org.

1 0

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

25 Feb '19

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

1 0

[CQ]: 98009,1 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 25 Feb '19

25 Feb '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 494 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Feb '19

25 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/494/ Build Number: 494 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #494 [Sandro Bonazzola] repos: master: switch to gluster 5 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.get_host_devices_42 Error Message: Could not find block_vda1 device in host devices: Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 1016, in get_host_devices raise RuntimeError('Could not find block_vda1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda1 device in host devices:

1 1

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

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Failed to run project_setup.sh for: #1389 containerized-data-importer [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-bxfjq.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Failed to run project_setup.sh for: #1390 containerized-data-importer [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-bjd42.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Failed to run project_setup.sh for: #1389 containerized-data-importer [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-9xgpc.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Failed to run project_setup.sh for: #1388 containerized-data-importer [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-kb8b6.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Failed to run project_setup.sh for: #1387 containerized-data-importer [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-rwdl1.

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #328
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/32…> Changes: [Liora Milbaum] master_deploy: versioned_value filter ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 798d77b25a396540dd740e97ba9075b6e3926310 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 798d77b25a396540dd740e97ba9075b6e3926310 # timeout=10 Commit message: "master_deploy: versioned_value filter" > git rev-list --no-walk 6d5cd8a6ec82ac556b4c414207b85536d44f39b8 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins1463866524962743710.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Failed to run project_setup.sh for: #1380 containerized-data-importer [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-41bfd.

1 0

Fwd: [GitHub] Subscribed to oVirt/ovirt-engine-sdk-go notifications
by Yaniv Kaul 24 Feb '19

24 Feb '19

Can we remove amureinin(a)redhat.com and aaviram(a)redhat.com from oVirt community? Both left Red Hat and I receive those notifications. Y. ---------- Forwarded message --------- From: GitHub <noreply(a)github.com> Date: Fri, Feb 22, 2019 at 7:33 PM Subject: [GitHub] Subscribed to oVirt/ovirt-engine-sdk-go notifications To: <amureini(a)redhat.com> Hey there, we’re just writing to let you know that you’ve been automatically subscribed to a repository on GitHub. oVirt/ovirt-engine-sdk-go Go SDK Generator for oVirt 4.x, with the help of oVirt community. https://github.com/oVirt/ovirt-engine-sdk-go You’ll receive notifications for all issues, pull requests, and comments that happen inside the repository. If you would like to stop watching this repository, you can manage your settings here: https://github.com/oVirt/ovirt-engine-sdk-go/subscription You can unwatch this repository immediately by clicking here: https://github.com/oVirt/ovirt-engine-sdk-go/unsubscribe_via_email/AD-wGfa9… You were automatically subscribed because you’ve been given access to the repository. Thanks!

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 493 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/493/ Build Number: 493 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #493 [Sandro Bonazzola] repos: master: switch to gluster 5 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.get_host_devices_41 Error Message: Could not find block_vda1 device in host devices: Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py", line 1016, in get_host_devices raise RuntimeError('Could not find block_vda1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda1 device in host devices:

1 1

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

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

1 0

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

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

1 0

Fwd: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC
by Sandro Bonazzola 22 Feb '19

22 Feb '19

FYI ---------- Forwarded message --------- From: Stephen John Smoogen <smooge(a)gmail.com> Date: ven 22 feb 2019 alle ore 20:43 Subject: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC To: <announce(a)lists.fedoraproject.org>, Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, Fedora Infrastructure < infrastructure(a)lists.fedoraproject.org> There will be an outage starting at 2019-02-27 20:00 UTC, which will last approximately 4-6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-27 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all core systems and services. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: All systems under fedoraproject.org will be affected. Important databases and authentication will be updated and rebooted first. Then other non-build systems will follow. Then build systems will finalize the update/reboot cycle Ticket Link: https://pagure.io/fedora-infrastructure/issue/7591 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[CQ]: 97986,1 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 22 Feb '19

22 Feb '19

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

1 0

[Ovirt] [CQ weekly status] [22-02-2019]
by Dafna Ron 22 Feb '19

22 Feb '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*: GREEN (#1) 1. rh-postgress was failing to start due to missing selinux policy causing engine to fail installation. Bug: https://bugzilla.redhat.com/show_bug.cgi Issue resolved by didi and Galit by: 1. adding a workaround to add the selinuc poslicy and also a proposed fix (as described in comment #6) 2. created new lago images with new selinux package *CQ-Master:* GREEN (#1) 1. The same issue in 4.2 has effected master (for upgrade suite) Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- 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)

1 0

[CQ]: 1a0df55 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Feb '19

22 Feb '19

Change 1a0df55 (ovirt-ansible-engine-setup) 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-engine-setup/commit/1a0df550b3014006… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3930/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 491 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Feb '19

22 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/491/ Build Number: 491 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #491 [jenkins CI] Add missing pkg: collectd-write_syslog [Sandro Bonazzola] ovirt-node-ng: stop building 4.2 and 4.2-pre [Gal Ben Haim] kubevirt-master: Add jobs [Tom�� Golembiovsk��] rename ovirt-ansible-v2v-conversion-host to v2v-conversion-host ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Feb '19

21 Feb '19

Failed to run project_setup.sh for: #1372 containerized-data-importer [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-hd8jz.

1 0

[CQ]: 92775,10 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

[CQ]: 97847,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Feb '19

21 Feb '19

Failed to run project_setup.sh for: #1369 containerized-data-importer [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-69rkd.

1 2

[CQ]: f434bb0 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

Change f434bb0 (ovirt-ansible-hosted-engine-setup) 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-hosted-engine-setup/commit/f434bb004… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3927/

1 0

[VDSM] check-patch job fail - Cannot download x86_64/ovirt-imageio-common-1.5.0-0.201901061027.gita4be4ca.fc28.x86_64.rpm: All mirrors were tried
by Nir Soffer 21 Feb '19

21 Feb '19

In this buidl: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/3035/artifact/ci_bu… 2 sub stages failed: This failed without generating any log, but we can see the error in the blue ocean interface: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/3035//artifact/chec… https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… This failed with this log: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/3035//artifact/chec… Both failed becasue: Cannot download x86_64/ovirt-imageio-common-1.5.0-0.201901061027.gita4be4ca.fc28.x86_64.rpm: All mirrors were tried The other sub stages succeeded, and building the patch on top succeeded: https://gerrit.ovirt.org/c/97847 Looks like temporary error, failing to find a package from tested repository? How can we prevent these errors? Nir

2 3

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Feb '19

21 Feb '19

Failed to run project_setup.sh for: #1369 containerized-data-importer [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-df90s.

1 0

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

21 Feb '19

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

1 0

[CQ]: 97795,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

[CQ]: 97929, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

[CQ]: 97928, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

[CQ]: 97873,5 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

Change 97873,5 (ovirt-engine) 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://gerrit.ovirt.org/#/c/97873/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3922/

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by Anton Marchukov (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1333: ----------------------------------- Resolution: Fixed Status: Done (was: To Do) I am resolving this as it was done at least partially. When we fill the gain from this is large enough to justify is larger then work required we will open a new ticket. > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: Icebox, first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by Barak Korren (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1333: ------------------------------------- I did when I removed the big packages (OVIRT-1332) - but there ar probably many more that can be removed if this is approached methodically. > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: Icebox, first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2681) please move ovirt-openshift-extensions to container based slaves
by Barak Korren (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2681?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2681: -------------------------------- Labels: ovirt-openshift-extensions (was: ) > please move ovirt-openshift-extensions to container based slaves > ---------------------------------------------------------------- > > Key: OVIRT-2681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2681 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, mock_runner > Reporter: Roy Golan > Assignee: infra > Labels: ovirt-openshift-extensions > > I'd like to use multi-stage container builds, please adjust > ovirt/ovirt-openshift-extensions project accordingly. > Thanks, > Roy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2681) please move ovirt-openshift-extensions to container based slaves
by Barak Korren (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2681?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2681: -------------------------------- Component/s: CI client projects Jenkins Slaves mock_runner > please move ovirt-openshift-extensions to container based slaves > ---------------------------------------------------------------- > > Key: OVIRT-2681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2681 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, mock_runner > Reporter: Roy Golan > Assignee: infra > > I'd like to use multi-stage container builds, please adjust > ovirt/ovirt-openshift-extensions project accordingly. > Thanks, > Roy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2681) please move ovirt-openshift-extensions to container based slaves
by Barak Korren (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2681?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2681: -------------------------------- Issue Type: New Feature (was: By-EMAIL) > please move ovirt-openshift-extensions to container based slaves > ---------------------------------------------------------------- > > Key: OVIRT-2681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2681 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roy Golan > Assignee: infra > > I'd like to use multi-stage container builds, please adjust > ovirt/ovirt-openshift-extensions project accordingly. > Thanks, > Roy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2681) please move ovirt-openshift-extensions to container based slaves
by Barak Korren (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2681?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2681: ------------------------------------- [~rgolan(a)redhat.com] I'm afraid we can't do that ATM, because container slaves are currently reserved for stuff that runs on bare metal. We'll need to containerize the VM slaves first. > please move ovirt-openshift-extensions to container based slaves > ---------------------------------------------------------------- > > Key: OVIRT-2681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > I'd like to use multi-stage container builds, please adjust > ovirt/ovirt-openshift-extensions project accordingly. > Thanks, > Roy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Martin Perina (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Martin Perina commented on OVIRT-2683: -------------------------------------- Thanks > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {noformat} > file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > {noformat} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Eyal Edri (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2683: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {noformat} > file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > {noformat} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97870,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Martin Perina (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Martin Perina commented on OVIRT-2683: -------------------------------------- OK, here's the patch https://gerrit.ovirt.org/97950 Could you please merge it? > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {noformat} > file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > {noformat} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Barak Korren (oVirt JIRA) 21 Feb '19

21 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2683: ------------------------------------- Hi Martin, I'm not sure why you're not able to edit the configuration from the gui, but you can probably submit the changes you need from the command line by running the following commands from a local engine clone: {code} git fetch origin refs/meta/config:meta-config git checkout meta-config {code} One you did that you can edit the {{reviewers.config}} file and then send a patch with: {code} git push origin HEAD:refs/for/refs/meta/config {code} > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {noformat} > file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > {noformat} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

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

1 0

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

20 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 20 Feb '19

20 Feb '19

Failed to run project_setup.sh for: #1365 containerized-data-importer [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-d4142.

1 2

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Martin Perina (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Martin Perina updated OVIRT-2683: --------------------------------- Description: Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? {noformat} file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com {noformat} Thanks Martin was: Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? {{ file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com }} Thanks Martin > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {noformat} > file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > {noformat} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Martin Perina (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Martin Perina updated OVIRT-2683: --------------------------------- Description: Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? {{ file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com }} Thanks Martin was: Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? {{file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com }} Thanks Martin > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {{ > file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > }} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Martin Perina (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2683?page=com.atlassian.jira.… ] Martin Perina updated OVIRT-2683: --------------------------------- Description: Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? {{file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com }} Thanks Martin was: Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com Thanks Martin > Add rules for default reviwewers > -------------------------------- > > Key: OVIRT-2683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > > Hi Evgheni, > I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. > Could you please add following rules so I'm notified automatically for relevant changes? > {{file:dao > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* > mperina(a)redhat.com > > file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* > mperina(a)redhat.com > > ^packaging/playbooks/.* > mperina(a)redhat.com > > ^packaging/dbscripts/.* > mperina(a)redhat.com > }} > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2683) Add rules for default reviwewers
by Martin Perina (oVirt JIRA) 20 Feb '19

20 Feb '19

Martin Perina created OVIRT-2683: ------------------------------------ Summary: Add rules for default reviwewers Key: OVIRT-2683 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2683 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Martin Perina Assignee: infra Hi Evgheni, I tried to change default reviewers using gerrit UI in the ovirt-engine project settings in Reviwers tab, but unfortunately it's readonly. Could you please add following rules so I'm notified automatically for relevant changes? file:dao mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/.*/hostdeploy/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/host/.* mperina(a)redhat.com file:^backend/manager/modules/.*/org/ovirt/engine/core/bll/pm/.* mperina(a)redhat.com ^packaging/playbooks/.* mperina(a)redhat.com ^packaging/dbscripts/.* mperina(a)redhat.com Thanks Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

20 Feb '19

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

1 0

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

20 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 20 Feb '19

20 Feb '19

Failed to run project_setup.sh for: #1364 containerized-data-importer [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-pmkwb.

1 0

[JIRA] (OVIRT-2670) ReadTheDocs content is out of date
by Evgheni Dereveanchin (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2670?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2670: ------------------------------------------- Assignee: Barak Korren (was: infra) > ReadTheDocs content is out of date > ---------------------------------- > > Key: OVIRT-2670 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2670 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Barak Korren > > I was trying to look up docs that were merged several weeks ago and couldn't find it. > Sample commit: > https://github.com/oVirt/infra-docs/commit/8ed6635042ef06d7ff7af7388ceb2fae… > Content in git: > https://github.com/oVirt/infra-docs/blob/master/docs/Phoenix_Lab/OpenShift.… > Section absent completely on RTD: > https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/OpenShift/ind… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

20 Feb '19

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

1 0

[JIRA] (OVIRT-2682) Add Pavel Bar to CI white-list
by Fred Rolland (oVirt JIRA) 20 Feb '19

20 Feb '19

Fred Rolland created OVIRT-2682: ----------------------------------- Summary: Add Pavel Bar to CI white-list Key: OVIRT-2682 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2682 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Fred Rolland Assignee: infra https://gerrit.ovirt.org/#/c/97869/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

20 Feb '19

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

1 0

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit
by Anton Marchukov (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1767: ---------------------------------------- I think most of the people browse the sources on GitHub mirror (myself included). Github has good sources browsers and search. -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: Icebox, gerrit > > One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ > Another plugin to consider is the one for using GitBlit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitblit is another Java based Gir bowser: > http://gitblit.com/features.html -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit
by Eyal Edri (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1767: ---------------------------------- I agree we don't have capacity or resources that justify going into such project now, just because gitweb isn't amazing and OK with closing it. but it has nothing to do with the GitHub mirroring. > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: Icebox, gerrit > > One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ > Another plugin to consider is the one for using GitBlit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitblit is another Java based Gir bowser: > http://gitblit.com/features.html -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

2 1

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

20 Feb '19

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

1 0

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

20 Feb '19

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

1 0

[CQ]: 97845,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 20 Feb '19

20 Feb '19

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

1 0

[CQ]: 97906, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Feb '19

20 Feb '19

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

1 0

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

20 Feb '19

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

1 0

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

20 Feb '19

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

1 0

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

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

1 0

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

19 Feb '19

Change 97886,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/97886/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13034/

1 0

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

19 Feb '19

Failed to run project_setup.sh for: #3668 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-46q2c.

1 0

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

19 Feb '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc28-x86_64 #883
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

1 1

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

19 Feb '19

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

1 0

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

19 Feb '19

Failed to run project_setup.sh for: #3663 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-1s9z1.

1 0

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

19 Feb '19

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

1 0

Re: [ovirt-devel] Re: ovirt-engine has been tagged (ovirt-engine-4.3.1)
by Sandro Bonazzola 19 Feb '19

19 Feb '19

Il giorno mar 19 feb 2019 alle ore 15:59 Tal Nisan <tnisan(a)redhat.com> ha scritto: > > > On Tue, Feb 19, 2019 at 1:22 PM Greg Sheremeta <gshereme(a)redhat.com> > wrote: > >> >> >> On Tue, Feb 19, 2019 at 4:41 AM Tal Nisan <tnisan(a)redhat.com> wrote: >> >>> >>> >>> On Tue, Feb 19, 2019 at 11:30 AM Doron Fediuck <dfediuck(a)redhat.com> >>> wrote: >>> >>>> >>>> >>>> On Tue, 19 Feb 2019 at 11:14, Tal Nisan <tnisan(a)redhat.com> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Feb 19, 2019 at 11:03 AM Doron Fediuck <dfediuck(a)redhat.com> >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tue, 19 Feb 2019 at 10:56, Tal Nisan <tnisan(a)redhat.com> wrote: >>>>>> >>>>>>> OK seems like I've found the reason, Ori you merged this patch >>>>>>> between the time when the version bumps were pushed and their actual merge >>>>>>> which cause them to rebase on the broken patch - >>>>>>> https://gerrit.ovirt.org/#/c/96610/ >>>>>>> Note that Jenkins failed on patchset 12 while CI was marked as +1 >>>>>>> manually (I guess wrongly based on the fact the artifacts were successfully >>>>>>> build but that does not mean tests passed) >>>>>>> >>>>>>> >>>>>> As a next step I'd like to know how do we avoid it next time? >>>>>> >>>>> Really hard to avoid, there's not many chance for that to happen since >>>>> the time window is quite short, if we decide to keep on rebasing the >>>>> version bumps it will not help much because Jenkins is still taking quite a >>>>> lot of time and potentially broken patches can be merged at this point. >>>>> What we can do is set a no-merge time in this specific time frame >>>>> (only if building from master, on the stable branches the maintainers take >>>>> care of all merges so no problem there) in which no one will merge patches >>>>> to keep stability >>>>> >>>> >>>> Will a maintainers' mailing list (single for all ovirt projects) help >>>> here or would we prefer a mutex somewhere? >>>> >>> Given the short time window in which this can happen I think the devel >>> list should do, a short email of "build is about to go soon, please hold >>> your merges until engine has been tagged" will probably be enough >>> >> >> I've found that many developers filter devel and other mailing lists into >> labels and infrequently check them. Not sure this will work. >> > That's a pity, it means no list will actually work cause the same people > who filter devel will filter the others. > Sando, any easy way in Gerrit to disable merges to a certain project and > then bring it back? > > No idea, adding infra > >> >>> >>>>>> >>>>>>> >>>>>>> On Tue, Feb 19, 2019 at 10:50 AM Tal Nisan <tnisan(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>>> I don't get it, both version bump patches passed Jenkins with all >>>>>>>> unit tests: >>>>>>>> https://gerrit.ovirt.org/#/c/97835 >>>>>>>> And the Jenkins job: >>>>>>>> >>>>>>>> https://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/48… >>>>>>>> >>>>>>>> Fred, what is the suspected patch that broke the tests? I suspect >>>>>>>> Gerrit auto rebase might broke something in case the version bump patches >>>>>>>> were not fully rebased on master when they were pushed >>>>>>>> >>>>>>>> On Tue, Feb 19, 2019 at 9:51 AM Fred Rolland <frolland(a)redhat.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> This fixes the failing test: >>>>>>>>> https://gerrit.ovirt.org/#/c/97865/ >>>>>>>>> >>>>>>>>> On Tue, Feb 19, 2019 at 9:28 AM Benny Zlotnik <bzlotnik(a)redhat.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I created a revert patch last night: >>>>>>>>>> https://gerrit.ovirt.org/#/c/97854/ >>>>>>>>>> >>>>>>>>>> frolland is currently checking if it's easy to fix without >>>>>>>>>> reverting >>>>>>>>>> >>>>>>>>>> On Tue, Feb 19, 2019, 09:18 Sandro Bonazzola <sbonazzo(a)redhat.com >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> please note engine build failed with: >>>>>>>>>>> >>>>>>>>>>> *17:45:54* [ERROR] Tests run: 11, Failures: 0, Errors: 3, Skipped: 1, Time elapsed: 0.258 s <<< FAILURE! - in org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest*17:45:54* [ERROR] testAdd Time elapsed: 0.027 s <<< ERROR!*17:45:54* org.ovirt.engine.api.restapi.utils.MappingException: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAdd(BackendAttachedStorageDomainsResourceTest.java:75)*17:45:54* Caused by: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAdd(BackendAttachedStorageDomainsResourceTest.java:75)*17:45:54* Caused by: java.lang.NullPointerException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAdd(BackendAttachedStorageDomainsResourceTest.java:75)*17:45:54* *17:45:54* [ERROR] testList Time elapsed: 0.018 s <<< ERROR!*17:45:54* org.ovirt.engine.api.restapi.utils.MappingException: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.getCollection(BackendAttachedStorageDomainsResourceTest.java:251)*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testList(BackendAttachedStorageDomainsResourceTest.java:179)*17:45:54* Caused by: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.getCollection(BackendAttachedStorageDomainsResourceTest.java:251)*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testList(BackendAttachedStorageDomainsResourceTest.java:179)*17:45:54* Caused by: java.lang.NullPointerException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.getCollection(BackendAttachedStorageDomainsResourceTest.java:251)*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testList(BackendAttachedStorageDomainsResourceTest.java:179)*17:45:54* *17:45:54* [ERROR] testAddByName Time elapsed: 0.022 s <<< ERROR!*17:45:54* org.ovirt.engine.api.restapi.utils.MappingException: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAddByName(BackendAttachedStorageDomainsResourceTest.java:116)*17:45:54* Caused by: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAddByName(BackendAttachedStorageDomainsResourceTest.java:116)*17:45:54* Caused by: java.lang.NullPointerException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAddByName(BackendAttachedStorageDomainsResourceTest.java:116)*17:45:54* *17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.LinkFollowerTest*17:45:54* [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 s - in org.ovirt.engine.api.restapi.util.LinkFollowerTest*17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.FenceOptionsParserTest*17:45:54* ERROR org.ovirt.engine.api.restapi.util.FenceOptionsParser - No type specified for fencing option "one".*17:45:54* ERROR org.ovirt.engine.api.restapi.util.FenceOptionsParser - Invalid fencing option description "three".*17:45:54* ERROR org.ovirt.engine.api.restapi.util.FenceOptionsParser - Invalid fencing agent description "foo:::one=1,two=2,three=3".*17:45:54* [INFO] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 s - in org.ovirt.engine.api.restapi.util.FenceOptionsParserTest*17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.LinkHelperTest*17:45:54* [INFO] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 s - in org.ovirt.engine.api.restapi.util.LinkHelperTest*17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.QueryHelperTest*17:45:54* [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in org.ovirt.engine.api.restapi.util.QueryHelperTest*17:45:55* [INFO] *17:45:55* [INFO] Results:*17:45:55* [INFO] *17:45:55* [ERROR] Failures: *17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemoveCantDo:181->doTestBadRemove:203 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemoveFailed:186->doTestBadRemove:203 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendStorageDomainResourceTest.testConflictedUpdate:175 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendStorageDomainResourceTest.testUpdateCantDo:145->doTestBadUpdate:164 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendStorageDomainResourceTest.testUpdateFailed:150->doTestBadUpdate:164 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] Errors: *17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testGet:69 ? Mapping java.lang.reflec...*17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemove:152 ? Mapping java.lang.re...*17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemoveLocalStorage:176 ? Mapping ...*17:45:55* [ERROR] BackendAttachedStorageDomainsResourceTest.testAdd:75 ? Mapping java.lang.refle...*17:45:55* [ERROR] BackendAttachedStorageDomainsResourceTest.testAddByName:116 ? Mapping java.lan...*17:45:55* [ERROR] BackendAttachedStorageDomainsResourceTest.testList:179->getCollection:251 ? Mapping*17:45:55* [ERROR] BackendStorageDomainResourceTest.testGet:79 ? Mapping java.lang.reflect.Invoca...*17:45:55* [ERROR] BackendStorageDomainResourceTest.testGetFcp:91 ? Mapping java.lang.reflect.Inv...*17:45:55* [ERROR] BackendStorageDomainResourceTest.testUpdate:140 ? Mapping java.lang.reflect.In...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddExistingStorageDomain:169->doTestAddStorageDomain:211 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddIscsiStorageDomain:348 ? Mapping java...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddIscsiStorageDomainAssumingConnection:392 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddLocalStorageDomain:251 ? Mapping java...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddPosixStorageDomain:301 ? Mapping java...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddStorageDomain:82->doTestAddStorageDomain:211 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddStorageDomainWithExistingConnectionId:128 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddStorageDomainWithHostName:162->doTestAddStorageDomain:211 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest>AbstractBackendCollectionResourceTest.testList:72->getCollection:634 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest>AbstractBackendCollectionResourceTest.testQuery:81->getCollection:634 ? Mapping*17:45:55* [INFO] *17:45:55* [ERROR] Tests run: 1849, Failures: 5, Errors: 19, Skipped: 65*17:45:55* [INFO] *17:45:55* [INFO] ------------------------------------------------------------------------*17:45:55* [INFO] Reactor Summary:*17:45:55* [INFO] *17:45:55* [INFO] oVirt Findbugs Filters ............................ SUCCESS [1.970s]*17:45:55* [INFO] ovirt-root ........................................ SUCCESS [3.307s]*17:45:55* [INFO] oVirt Build Tools root ............................ SUCCESS [1.213s]*17:45:55* [INFO] oVirt checkstyle .................................. SUCCESS [2.121s]*17:45:55* [INFO] oVirt Checkstyle Checks ........................... SUCCESS [3.430s]*17:45:55* [INFO] oVirt Modules - backend ........................... SUCCESS [0.734s]*17:45:55* [INFO] oVirt Manager ..................................... SUCCESS [0.738s]*17:45:55* [INFO] oVirt Engine dependencies ......................... SUCCESS [0.891s]*17:45:55* [INFO] oVirt Engine common dependencies .................. SUCCESS [3.350s]*17:45:55* [INFO] oVirt Engine tools dependencies ................... SUCCESS [0.813s]*17:45:55* [INFO] Utilities to extend java.logging framework ........ SUCCESS [1.682s]*17:45:55* [INFO] Extensions API root ............................... SUCCESS [0.005s]*17:45:55* [INFO] ovirt-engine-extensions-api ....................... SUCCESS [9.274s]*17:45:55* [INFO] oVirt Modules - manager ........................... SUCCESS [2.056s]*17:45:55* [INFO] Universal utilities ............................... SUCCESS [20.282s]*17:45:55* [INFO] Extensions manager ................................ SUCCESS [5.412s]*17:45:55* [INFO] GWT UI Compatibility .............................. SUCCESS [6.178s]*17:45:55* [INFO] Common Code ....................................... SUCCESS [36.381s]*17:45:55* [INFO] Common utilities .................................. SUCCESS [35.291s]*17:45:55* [INFO] Branding package .................................. SUCCESS [9.146s]*17:45:55* [INFO] ovirt-engine sso .................................. SUCCESS [5.829s]*17:45:55* [INFO] Data Access Layer ................................. SUCCESS [30.876s]*17:45:55* [INFO] engine scheduler bean ............................. SUCCESS [6.888s]*17:45:55* [INFO] Vds broker ........................................ SUCCESS [32.916s]*17:45:55* [INFO] builtin-extensions ................................ SUCCESS [2.320s]*17:45:55* [INFO] Search Backend .................................... SUCCESS [10.064s]*17:45:55* [INFO] Backend Authentication, Authorization and Accounting SUCCESS [7.355s]*17:45:55* [INFO] Custom Application Server Authentication Plugin ... SUCCESS [3.320s]*17:45:55* [INFO] Backend Logic @Service bean ....................... SUCCESS [2:51.560s]*17:45:55* [INFO] oVirt RESTful API Backend Integration ............. SUCCESS [1.084s]*17:45:55* [INFO] oVirt RESTful API interface ....................... SUCCESS [1.005s]*17:45:55* [INFO] oVirt Engine API Definition ....................... SUCCESS [50.498s]*17:45:55* [INFO] oVirt Engine API Commom Parent POM ................ SUCCESS [1.037s]*17:45:55* [INFO] oVirt Engine API Common JAX-RS .................... SUCCESS [8.077s]*17:45:55* [INFO] oVirt RESTful API Backend Integration Type Mappers SUCCESS [22.779s]*17:45:55* [INFO] oVirt RESTful API Backend Integration JAX-RS Resources FAILURE [1:52.179s] >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Job is here: >>>>>>>>>>> https://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_6… >>>>>>>>>>> >>>>>>>>>>> So we need a respin once fixed. >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> SANDRO BONAZZOLA >>>>>>>>>>> >>>>>>>>>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>>>>>>>>>> >>>>>>>>>>> Red Hat EMEA <https://www.redhat.com/> >>>>>>>>>>> >>>>>>>>>>> sbonazzo(a)redhat.com >>>>>>>>>>> <https://red.ht/sig> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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/2GJAJHWAD5X43… >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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/32XDCPM6IPOD7… >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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/LV6XFFQPI4ZFZ… >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>> 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/THBBN6G2ETAEE… >>>>>>> >>>>>> _______________________________________________ >>> 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/ZG57PMU7GKJ57… >>> >> >> >> -- >> >> 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> >> > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

3 2

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

19 Feb '19

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

1 0

[CQ]: 96986, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

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

1 0

[CQ]: 96743, 5 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

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

1 0

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

19 Feb '19

Failed to run project_setup.sh for: #3650 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-2flgx.

1 0

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

19 Feb '19

A system test invoked by the "ovirt-master" change queue including change 07c7fd2 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 7d67266 (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 7d67266 (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/07c7fd24e2ae3d824a60a6951ceb97… 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/7d6726676871274417e78139507a96… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13018/

1 0

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

19 Feb '19

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

1 0

[CQ]: 97677,7 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 19 Feb '19

19 Feb '19

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

1 0

[CQ]: 97818, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

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

1 0

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

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

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3643 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-052rf.

1 0

[CQ]: 97818, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

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

1 0

[CQ]: 97817, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97817, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[vdsm]jenkins build on demand doesn't seem to work on stable branch
by Francesco Romani 18 Feb '19

18 Feb '19

Hi Infra, I'd like to build RPMs using "ci please build" for my https://gerrit.ovirt.org/#/c/97737/ - the ultimate goal is to have OST validate my patch. It seems to me that the "ci please build" command isn't working, or at least I can't see any feedback about it. Is this automation still enabeld for the stable branch? Any idea what's going on? Thanks, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

2 2

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

18 Feb '19

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

1 0

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

18 Feb '19

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

1 0

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

18 Feb '19

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

1 0

After import storage many of my vm's disks not appear
by Kalil de A. Carvalho 18 Feb '19

18 Feb '19

Hello all. It is been a while that I used the oVirt and on the same time, the company where I started to work, has a big problem with the engine, we lose it. We did not have any backup. To try recovery the enverioment I installed a knew oVirt, this time Hosted Engine, and import the Storage. I could import and start some vm's but the most part not appear for me, dosen't show on "Disk Import", "VM Import" and any place. I know that is there, because show me that size. May I see, like list, this disks? I can't do this throught oVirt web. Is there any way to bring dist disks back? I already search this tasks but with no luck. oVirt ver: 4.2.8.2-1.el7 Any one can help, please? Best regards. -- Atenciosamente, Kalil de A. Carvalho

2 1

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

18 Feb '19

Failed to run project_setup.sh for: #3634 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-40p3c.

1 0

[CQ]: 96986, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 4d1eb83 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 4d1eb83 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 52f05b8 (ovirt-ansible- hosted-engine-setup) 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 52f05b8 (ovirt-ansible-hosted- engine-setup) 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-hosted-engine-setup/commit/4d1eb83a0… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12976/

1 0

[CQ]: 07c7fd2 (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 07c7fd2 (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/07c7fd24e2ae3d824a60a6951ceb97… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3899/

1 0

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

18 Feb '19

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

1 0

[CQ]: 97819,1 (ovirt-host) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97819,1 (ovirt-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://gerrit.ovirt.org/#/c/97819/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12972/

1 0

[CQ]: 96984, 18 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

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

1 0

[CQ]: 96980, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 7f83b03 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 7f83b03 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 52f05b8 (ovirt-ansible- hosted-engine-setup) 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 52f05b8 (ovirt-ansible-hosted- engine-setup) 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-hosted-engine-setup/commit/7f83b03f8… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12960/

1 0

[CQ]: 97729,7 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #1326 containerized-data-importer [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-6tqnq.

1 0

[CQ]: 97257, 24 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

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

1 0

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

18 Feb '19

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

1 0