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