- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 266 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 May '18

15 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x8… Build Number: 266 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #266 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran.

1 6

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 67 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 May '18

15 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/6… Build Number: 67 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #67 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran.

1 6

[JIRA] (OVIRT-2023) mailing lists footer macros are broken
by Marc Dequènes (Duck) (oVirt JIRA) 15 May '18

15 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2023?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2023: ---------------------------------------- Attachment: signature.asc A little test before replying… > mailing lists footer macros are broken > -------------------------------------- > > Key: OVIRT-2023 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2023 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > Attachments: signature.asc > > > mailing lists footer macros are broken. Examples: > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > -- > 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#100085)

1 0

[CQ]: 91226, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '18

15 May '18

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

1 0

[CQ]: 90968, 14 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '18

15 May '18

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

1 0

[CQ]: 90967, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '18

15 May '18

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

1 0

[CQ]: 90966, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '18

15 May '18

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

1 0

[CQ]: 90965, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '18

15 May '18

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

1 0

[CQ]: 91183, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '18

14 May '18

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

1 0

[CQ]: 89266, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '18

14 May '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 148 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 May '18

14 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 148 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #148 [Your Name] networking: Introducing create_vnic method for virtlib.Vm ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_he_hosts Error Message: Host lago-he-basic-iscsi-suite-master-host-1 is in non operational state -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _he_host_is_up_4 at 0x7f5c7f643f50> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_he-basic-iscsi-suite-master/ovirt-system-tests/he-basic-iscsi-suite-master/test-scenarios/002_bootstrap.py", line 389, in _he_host_is_up_4 raise RuntimeError('Host %s is in non operational state' % api_host.name) RuntimeError: Host lago-he-basic-iscsi-suite-master-host-1 is in non operational state --------------------- >> 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-iscsi-suite-master/ovirt-system-tests/he-basic-iscsi-suite-master/test-scenarios/002_bootstrap.py", line 358, in add_he_hosts add_he_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-iscsi-suite-master/ovirt-system-tests/he-basic-iscsi-suite-master/test-scenarios/002_bootstrap.py", line 404, in add_he_hosts_4 testlib.assert_true_within(_he_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_he-basic-iscsi-suite-master/ovirt-system-tests/he-basic-iscsi-suite-master/test-scenarios/002_bootstrap.py", line 389, in _he_host_is_up_4 raise RuntimeError('Host %s is in non operational state' % api_host.name) 'Host lago-he-basic-iscsi-suite-master-host-1 is in non operational state\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _he_host_is_up_4 at 0x7f5c7f643f50>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_he-basic-iscsi-suite-master/ovirt-system-tests/he-basic-iscsi-suite-master/test-scenarios/002_bootstrap.py", line 389, in _he_host_is_up_4\n raise RuntimeError(\'Host %s is in non operational state\' % api_host.name)\nRuntimeError: Host lago-he-basic-iscsi-suite-master-host-1 is in non operational state\n--------------------- >> end captured logging << ---------------------'

1 1

[CQ]: 90787, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '18

14 May '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 151 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 May '18

14 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/151/ Build Number: 151 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #151 [Gal Ben Haim] 4.1 basic: Increase verify_suspend_vm timeout [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup ----------------- Failed Tests: ----------------- No tests ran.

1 16

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Daniel Belenky (oVirt JIRA) 14 May '18

14 May '18

Daniel Belenky created OVIRT-2025: ------------------------------------- Summary: Document STDCI "V1.5" poll upstream sources jobs Key: OVIRT-2025 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 Project: oVirt - virtualization made easy Issue Type: Task Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: # How to create such job for a given project: implement a JJB temlpate # How to configure STDCI configuration file so poll-upstream-sources will work. If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Daniel Belenky (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2025?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2025: ---------------------------------- Epic Link: OVIRT-400 > Document STDCI "V1.5" poll upstream sources jobs > ------------------------------------------------ > > Key: OVIRT-2025 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: > # How to create such job for a given project: implement a JJB temlpate > # How to configure STDCI configuration file so poll-upstream-sources will work. > If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[CQ]: 85805,12 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 May '18

14 May '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 368 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 May '18

14 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/368/ Build Number: 368 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #368 [Marcin Mirecki] network: lookup ovn port by vnic id [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup ----------------- Failed Tests: ----------------- No tests ran.

1 16

[JIRA] (OVIRT-2024) virt-sparsify fails silently
by Dafna Ron (oVirt JIRA) 14 May '18

14 May '18

Dafna Ron created OVIRT-2024: -------------------------------- Summary: virt-sparsify fails silently Key: OVIRT-2024 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2024 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra virt-sparsify fails silently (intentionally silently). you can see the error in the host vdsm log (even on successful builds) 018-05-14 07:15:02,271-0400 ERROR (tasks/6) [root] Job u'796dd36e-0095-4adc-afb9-8b011f6b8ced' failed (jobs:221) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/jobs.py", line 157, in run self._run() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdm/api/sparsify_volume.py", line 56, in _run virtsparsify.sparsify_inplace(self._vol_info.path) File "/usr/lib/python2.7/site-packages/vdsm/virtsparsify.py", line 71, in sparsify_inplace raise cmdutils.Error(cmd, rc, out, err) Error: Command ['/usr/bin/virt-sparsify', '--machine-readable', '--in-place', u'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/96157fda-d60a-49d1-adb8-f306e402a0cf/images/156eaf32-5219-4be7-b61e-b5104f2b6c4d/77eb6602-13ac-46aa-a4 39-af9e51e3c2cb'] failed with rc=1 out=['3/12'] err=['virt-sparsify: error: libguestfs error: guestfs_launch failed.', 'This usually means the libguestfs appliance failed to start or crashed.', 'Do:', ' export LIBGUESTFS_DEBUG=1 LIBGUEST FS_TRACE=1', 'and run the command again. For further information, read:', ' http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs', "You can also run 'libguestfs-test-tool' and post the *complete* output", 'into a bug report or message to the libguestfs mailing list.', '', 'If reporting bugs, run virt-sparsify with debugging enabled and include the ', 'complete output:', '', ' virt-sparsify -v -x [...]'] 2018-05-14 07:15:02,273-0400 INFO (tasks/6) [root] Job u'796dd36e-0095-4adc-afb9-8b011f6b8ced' will be deleted in 3600 seconds (jobs:249) 2018-05-14 07:15:02,273-0400 DEBUG (tasks/6) [jsonrpc.Notification] Sending event {"params": {"status": "failed", "description": "sparsify_volume", "job_type": "storage", "error": {"message": "General Exception: ('Command [\\'/usr/bin/vir t-sparsify\\', \\'--machine-readable\\', \\'--in-place\\', u\\'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/96157fda-d60a-49d1-adb8-f306e402a0cf/images/156eaf32-5219-4be7-b61e-b5104f2b6c4d/77eb6602-13ac-46aa-a439-af9e51e3c2cb\\ '] failed with rc=1 out=[\\'3/12\\'] err=[\\'virt-sparsify: error: libguestfs error: guestfs_launch failed.\\', \\'This usually means the libguestfs appliance failed to start or crashed.\\', \\'Do:\\', \\' export LIBGUESTFS_DEBUG=1 LIBGU ESTFS_TRACE=1\\', \\'and run the command again. For further information, read:\\', \\' http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\', \"You can also run \\'libguestfs-test-tool\\' and post the *complete* output\", \\' into a bug report or message to the libguestfs mailing list.\\', \\'\\', \\'If reporting bugs, run virt-sparsify with debugging enabled and include the \\', \\'complete output:\\', \\'\\', \\' virt-sparsify -v -x [...]\\']',)", "code": 1 00}, "notify_time": 4295843980, "id": "796dd36e-0095-4adc-afb9-8b011f6b8ced"}, "jsonrpc": "2.0", "method": "|jobs|status|796dd36e-0095-4adc-afb9-8b011f6b8ced"} (__init__:180) 2018-05-14 07:15:02,273-0400 DEBUG (tasks/6) [vds] Sending notification |jobs|status|796dd36e-0095-4adc-afb9-8b011f6b8ced with params {'status': 'failed', 'description': 'sparsify_volume', 'job_type': 'storage', 'error': {'message': 'Gene ral Exception: (\'Command [\\\'/usr/bin/virt-sparsify\\\', \\\'--machine-readable\\\', \\\'--in-place\\\', u\\\'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/96157fda-d60a-49d1-adb8-f306e402a0cf/images/156eaf32-5219-4be7-b61e-b5 104f2b6c4d/77eb6602-13ac-46aa-a439-af9e51e3c2cb\\\'] failed with rc=1 out=[\\\'3/12\\\'] err=[\\\'virt-sparsify: error: libguestfs error: guestfs_launch failed.\\\', \\\'This usually means the libguestfs appliance failed to start or crash ed.\\\', \\\'Do:\\\', \\\' export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\', \\\'and run the command again. For further information, read:\\\', \\\' http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\', "You can also run \ \\'libguestfs-test-tool\\\' and post the *complete* output", \\\'into a bug report or message to the libguestfs mailing list.\\\', \\\'\\\', \\\'If reporting bugs, run virt-sparsify with debugging enabled and include the \\\', \\\'complet e output:\\\', \\\'\\\', \\\' virt-sparsify -v -x [...]\\\']\',)', 'code': 100}, 'notify_time': 4295843980, 'id': u'796dd36e-0095-4adc-afb9-8b011f6b8ced'} (clientIF:225) 2018-05-14 07:15:02,274-0400 INFO (tasks/6) [storage.ThreadPool.WorkerThread] FINISH task 041a7423-8c05-44b2-b3c9-6d5cf8710edc (threadPool:210) 2018-05-14 07:15:04,229-0400 DEBUG (qgapoller/1) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='e1317264-a572-47e0-98b4-d492239e285e', command is not supported (qemuguestagent:192) 2018-05-14 07:15:04,230-0400 DEBUG (qgapoller/2) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='29a56e04-51c7-4f25-b3c8-6df5489b2445', command is not supported (qemuguestagent:192) 2018-05-14 07:15:05,186-0400 DEBUG (vmchannels) [vds] Timeout on fileno 63. (vmchannels:126) Shmuel is investigating and we need to follow up with him. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Dafna Ron (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2021: ---------------------------------- Arik is investigating the failure and he thinks he knows the cause. I looked at CQ to try and see what the issue is and I can see 3 changes tested (all merged by Arik) and all 3 failed on the same issue. The first change ran here: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ and it was marked as failed due to https://gerrit.ovirt.org/#/c/91084/1 which I think was not fixed yet. hence, all other failures were marked with https://gerrit.ovirt.org/#/c/91084/1 in CQ. I asked Arik to let me know if he can pin point the failure to a specific patch but I am 99% sure it is the first one that failed. > CQ reporting wrong change as root cause > ---------------------------------------- > > Key: OVIRT-2021 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > For further details about the change see: > https://gerrit.ovirt.org/#/c/91188/2 > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/91084/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ > The failure is a time out which was caused by a NPE (which is a real bug). > CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[oVirt CI] standard-enqueue - Build #13397 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 May '18

14 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13397/ Build Name: #13397 Build Description: Gerrit: 91168 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91168 - title: ansible: Hotfix for Ansible yum module - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Martin Peřina <mperina(a)redhat.com>

1 0

[JIRA] (OVIRT-2023) mailing lists footer macros are broken
by Greg Sheremeta (oVirt JIRA) 14 May '18

14 May '18

Greg Sheremeta created OVIRT-2023: ------------------------------------- Summary: mailing lists footer macros are broken Key: OVIRT-2023 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2023 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra mailing lists footer macros are broken. Examples: > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s -- 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#100084)

1 0

[CQ]: 91180,1 (ovirt-dwh) failed "ovirt-master" system tests
by oVirt Jenkins 14 May '18

14 May '18

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

2 1

[CQ]: 91093, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '18

14 May '18

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

2 1

[JIRA] (OVIRT-2022) libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma
by Dafna Ron (oVirt JIRA) 14 May '18

14 May '18

Dafna Ron created OVIRT-2022: -------------------------------- Summary: libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma Key: OVIRT-2022 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2022 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra build-artifacts failing on http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/3508/c… The error is package missing for; 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements 12:20:11 Error: Package: 1:libguestfs-1.36.10-6.el7.centos.ppc64le (el) 12:20:11 Requires: qemu-img-ma 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7.ppc64le (el) 12:20:11 qemu-img-ma = 10:2.10.0-21.el7 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7_5.1.ppc64le (el-updates) 12:20:11 qemu-img-ma = 10:2.10.0-21.el7_5.1 12:20:11 You could try using --skip-broken to work around the problem 12:20:11 You could try running: rpm -Va --nofiles --nodigest 12:20:11 12:20:11 Init took 28 seconds 12:20:11 ============================ 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 12:20:11 @@ Thu May 10 12:20:11 UTC 2018 automation/build-artifacts.sh chroot finished 12:20:11 @@ took 28 seconds 12:20:11 @@ rc = 1 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 12:20:11 ========== Scrubbing chroot 12:20:11 mock \ The issue is with centos: https://bugzilla.redhat.com/show_bug.cgi?id=1570533 The 7.5.1 should come out tomorrow and this issue will be fixed opening ticket to follow up and make sure that its back to normal tomorrow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

Re: Can you please have a look at this failure?
by Yedidyah Bar David 14 May '18

14 May '18

On Mon, May 14, 2018 at 9:47 AM, Shirly Radco <sradco(a)redhat.com> wrote: > > Good morning, > > I have an issue with DWH in fc27, missing packages. > http://jenkins.ovirt.org/job/ovirt-dwh_master_check-patch-fc27-x86_64/24/co… > 08:34:21 Error: No Package found for apache-commons-collections > 08:34:21 Error: No Package found for ovirt-engine-wildfly > > Can you please help me with how to fix it? Adding infra. Seems like the job ran on fc26: 08:26:53 Building remotely on vm0061.workers-phx.ovirt.org (libvirt phx nested fc26) in workspace /home/jenkins/workspace/ovirt-dwh_master_check-patch-fc27-x86_64 Is that intended? Thanks, -- Didi

2 4

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 786 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 May '18

14 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 786 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #786 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Yuval Turgeman] scripts: let virt-install handle shutdown ----------------- Failed Tests: ----------------- No tests ran.

1 5

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2021: ------------------------------------- so why did the test that checked the root cause change fail? > CQ reporting wrong change as root cause > ---------------------------------------- > > Key: OVIRT-2021 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > For further details about the change see: > https://gerrit.ovirt.org/#/c/91188/2 > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/91084/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ > The failure is a time out which was caused by a NPE (which is a real bug). > CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Dafna Ron (oVirt JIRA) 14 May '18

14 May '18

Dafna Ron created OVIRT-2021: -------------------------------- Summary: CQ reporting wrong change as root cause Key: OVIRT-2021 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause For further details about the change see: https://gerrit.ovirt.org/#/c/91188/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91084/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ The failure is a time out which was caused by a NPE (which is a real bug). CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[CQ]: 91144, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '18

14 May '18

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

1 0

[JIRA] (OVIRT-2019) users can't unsubscribe from list
by Marc Dequènes (Duck) (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2019?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2019: ---------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) Status: In Progress (was: To Do) I looked into the logs and found traces similar to the previous bug ("Connection lost during _handle_client()", see https://gitlab.com/mailman/mailman/issues/416) After migration people began to use the ML again and this bug reappeared, but only for the gerrit ML. I fixed the DB manually and it did not reappear. This might be related. I subscribed and tried to unsubcribe from the UI and it worked. If I use the leave address instead, the previous trace occur but I shortly after (there is a delay due to greylisting) received the confirmation mail; I replied and it worked. > users can't unsubscribe from list > ---------------------------------- > > Key: OVIRT-2019 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2019 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: Marc Dequènes (Duck) > Priority: Highest > > There has been multiple reports from users on users(a)ovirt.org that they can't un-subscribe from the list, either using the UI or the leave ML alias. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2018?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2018: ----------------------------------- Assignee: Emil Natan (was: infra) > Add documentation for the stdci_conf_check.py utility > ----------------------------------------------------- > > Key: OVIRT-2018 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Emil Natan > Assignee: Emil Natan > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2018?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2018: -------------------------------- Epic Link: OVIRT-400 Priority: High (was: Low) > Add documentation for the stdci_conf_check.py utility > ----------------------------------------------------- > > Key: OVIRT-2018 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Emil Natan > Assignee: infra > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2018?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2018: -------------------------------- Epic Link: OVIRT-400 > Add documentation for the stdci_conf_check.py utility > ----------------------------------------------------- > > Key: OVIRT-2018 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Emil Natan > Assignee: infra > Priority: Low > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

Re: [ovirt-users] Re: [ovirt-devel] Re: Mailing-Lists upgrade
by Marc Dequènes (Duck) 14 May '18

14 May '18

Quack, On 05/13/2018 08:27 PM, Alex K wrote: > I am also experiencing random issues with this mailing list, even before > the upgrade. Some replies I never receive them ( I know this because a > friend of mine relays the emails I dont get...). I tried to unsubscribe > and subscribe but I still face this issue. Well, as it happened before the migration I guess it's more of mail antispam & co problem. Could you open a JIRA ticket with as much information as you can on the subject please? I'm going to focus on migration problems first, but I'll a look at it afterwards. \_o<

1 0

[CQ]: 91128, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 May '18

13 May '18

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

1 0

[CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 May '18

13 May '18

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

1 0

[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2020?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2020: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Implement a normalizer for runtime_requirements > ----------------------------------------------- > > Key: OVIRT-2020 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Currently, we are not parsing the data under runtime_requirements at all. > It means that the 1st place user will encounter an error is when the job runs - > it's bad since debugging it is much harder than our DSL. > Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in > standard-stage.groovy that verifies the value of some inputs under runtime_requirements. > It should be removed as soon as a proper normalizer is implemented. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA) 13 May '18

13 May '18

Daniel Belenky created OVIRT-2020: ------------------------------------- Summary: Implement a normalizer for runtime_requirements Key: OVIRT-2020 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020 Project: oVirt - virtualization made easy Issue Type: Task Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra Currently, we are not parsing the data under runtime_requirements at all. It means that the 1st place user will encounter an error is when the job runs - it's bad since debugging it is much harder than our DSL. Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in standard-stage.groovy that verifies the value of some inputs under runtime_requirements. It should be removed as soon as a proper normalizer is implemented. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2020?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2020: ---------------------------------- Epic Link: OVIRT-400 > Implement a normalizer for runtime_requirements > ----------------------------------------------- > > Key: OVIRT-2020 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Currently, we are not parsing the data under runtime_requirements at all. > It means that the 1st place user will encounter an error is when the job runs - > it's bad since debugging it is much harder than our DSL. > Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in > standard-stage.groovy that verifies the value of some inputs under runtime_requirements. > It should be removed as soon as a proper normalizer is implemented. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2019) users can't unsubscribe from list
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2019?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2019: ----------------------------- Epic Link: OVIRT-403 > users can't unsubscribe from list > ---------------------------------- > > Key: OVIRT-2019 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2019 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > Priority: Highest > > There has been multiple reports from users on users(a)ovirt.org that they can't un-subscribe from the list, either using the UI or the leave ML alias. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2019) users can't unsubscribe from list
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

eyal edri created OVIRT-2019: -------------------------------- Summary: users can't unsubscribe from list Key: OVIRT-2019 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2019 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri Assignee: infra Priority: Highest There has been multiple reports from users on users(a)ovirt.org that they can't un-subscribe from the list, either using the UI or the leave ML alias. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Emil Natan (oVirt JIRA) 13 May '18

13 May '18

Emil Natan created OVIRT-2018: --------------------------------- Summary: Add documentation for the stdci_conf_check.py utility Key: OVIRT-2018 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 Project: oVirt - virtualization made easy Issue Type: Task Components: Documentation Reporter: Emil Natan Assignee: infra Priority: Low -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2017) Add fc28 slave to jenkins
by Gal Ben Haim (oVirt JIRA) 13 May '18

13 May '18

Gal Ben Haim created OVIRT-2017: ----------------------------------- Summary: Add fc28 slave to jenkins Key: OVIRT-2017 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2017 Project: oVirt - virtualization made easy Issue Type: Bug Components: Lago Reporter: Gal Ben Haim Assignee: infra fc28 slave is required for lago's check-patch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1465: ----------------------------------- Assignee: Barak Korren (was: infra) > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > Labels: jenkins, jjb, standard-ci > > Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1465: -------------------------------- Description: Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo. Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. was: Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo. Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, jjb, standard-ci > > Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2015: ------------------------------------- [~eedri] I see. [~dron] - just for the sake of full RCA - lets find the smoking gun here and see if the patch was indeed merged with CI that failed on this. Lets think if we can make a short lesson to the team about this kind of incident in one way or another (E.g in email or in the MTG tomorrow). > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

Please help unsubscribing inactive members
by Yaniv Kaul 13 May '18

13 May '18

Vered left, but Allon could not / did not cancel her subscription. Now Allon left, and I'm getting the emails: Delivered-To: ykaul(a)redhat.com Received: by smtp.corp.redhat.com (Postfix, from userid 8) id 0082F3001656; Sun, 13 May 2018 06:53:57 +0000 (UTC) X-Original-To: amureini Delivered-To: amureini(a)redhat.com Received: by smtp.corp.redhat.com (Postfix, from userid 8) id E64673001641; Sun, 13 May 2018 06:53:57 +0000 (UTC) X-Original-To: vvolansk(a)redhat.com Delivered-To: vvolansk(a)redhat.com Can we somehow remove vvolansk(a)redhat.com from infra(a)ovirt.org?

2 4

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2015: ---------------------------------- It might have failed and I missed it, due to the will to solve the 7.5 and 4.1 issues fast, I think I might have thought the failure was reposync related and it will get fixed once I open the master repos. > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2015: ------------------------------------- [~eedri] yeah , I chatted with [~dron] about this a little - the thing we need to check here is why the OST check-patch didn't catch this for us. > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2015: ---------------------------------- CQ can also fail on OST test change, which is not (yet) a CQ object, you have to take that into account when debugging failures. so I'm not sure this is a real issue. [~bkorren(a)redhat.com] > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0