- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 43 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 May '20

29 May '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 43 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #43 [Yedidyah Bar David] HE: try to get status multiple times [Ehud Yonasi] ost_nightly: added jobs for nightly tests. ----------------- Failed Tests: ----------------- No tests ran.

1 3

[oVirt Jenkins] ovirt-system-tests_upgrade-from-release-suite-4.3_nightly - Build # 1 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 May '20

29 May '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_upgrade-from-release-suite… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_upgrade-from-release-suite… Build Number: 1 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

1 3

oVirt infra daily report - unstable production jobs - 1205
by jenkins＠jenkins.phx.ovirt.org 29 May '20

29 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1205//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2949) Please upgrade oVirt datacenter to 4.4
by Sandro Bonazzola (oVirt JIRA) 28 May '20

28 May '20

Sandro Bonazzola created OVIRT-2949: --------------------------------------- Summary: Please upgrade oVirt datacenter to 4.4 Key: OVIRT-2949 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2949 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra Now that oVirt 4.4.0 has been released, we should upgrade oVirt datacenter to 4.4. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[CQ]: 109329, 1 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '20

28 May '20

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

1 0

[CQ]: 109329, 1 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '20

28 May '20

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

1 0

oVirt infra daily report - unstable production jobs - 1204
by jenkins＠jenkins.phx.ovirt.org 28 May '20

28 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1204//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 109012, 3 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 May '20

27 May '20

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

1 0

[CQ]: 109012, 3 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 May '20

27 May '20

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

1 0

oVirt infra daily report - unstable production jobs - 1203
by jenkins＠jenkins.phx.ovirt.org 27 May '20

27 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1203//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 109291,1 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 26 May '20

26 May '20

Change 109291,1 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/109291/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23916/

1 0

[JIRA] (OVIRT-2948) [FIRING:1] InstanceUnreachable (amd64 linux shift-m02.phx.ovirt.org kubernetes-nodes-exporter shift-m02.phx.ovirt.org true true infra default)
by Shlomi Zidmi (oVirt JIRA) 26 May '20

26 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2948?page=com.atlassian.jira.… ] Shlomi Zidmi reassigned OVIRT-2948: ----------------------------------- Assignee: Shlomi Zidmi (was: infra) > [FIRING:1] InstanceUnreachable (amd64 linux shift-m02.phx.ovirt.org kubernetes-nodes-exporter shift-m02.phx.ovirt.org true true infra default) > ---------------------------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2948 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2948 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Alertmanager_Bot > Assignee: Shlomi Zidmi > Labels: ALERT{alertname="InstanceUnreachable"} > > Labels: > - alertname = InstanceUnreachable > - beta_kubernetes_io_arch = amd64 > - beta_kubernetes_io_os = linux > - instance = shift-m02.phx.ovirt.org > - job = kubernetes-nodes-exporter > - kubernetes_io_hostname = shift-m02.phx.ovirt.org > - logging_infra_fluentd = true > - node_role_kubernetes_io_master = true > - region = infra > - zone = default > Annotations: > - description = shift-m02.phx.ovirt.org of job kubernetes-nodes-exporter has been down for more than 10 minutes. > Source: http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-expor… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[JIRA] (OVIRT-2948) [FIRING:1] InstanceUnreachable (amd64 linux shift-m02.phx.ovirt.org kubernetes-nodes-exporter shift-m02.phx.ovirt.org true true infra default)
by Alertmanager_Bot (oVirt JIRA) 26 May '20

26 May '20

Alertmanager_Bot created OVIRT-2948: --------------------------------------- Summary: [FIRING:1] InstanceUnreachable (amd64 linux shift-m02.phx.ovirt.org kubernetes-nodes-exporter shift-m02.phx.ovirt.org true true infra default) Key: OVIRT-2948 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2948 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Alertmanager_Bot Assignee: infra Labels: - alertname = InstanceUnreachable - beta_kubernetes_io_arch = amd64 - beta_kubernetes_io_os = linux - instance = shift-m02.phx.ovirt.org - job = kubernetes-nodes-exporter - kubernetes_io_hostname = shift-m02.phx.ovirt.org - logging_infra_fluentd = true - node_role_kubernetes_io_master = true - region = infra - zone = default Annotations: - description = shift-m02.phx.ovirt.org of job kubernetes-nodes-exporter has been down for more than 10 minutes. Source: http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-expor… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

oVirt infra daily report - unstable production jobs - 1202
by jenkins＠jenkins.phx.ovirt.org 26 May '20

26 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1202//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 109243, 2 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109243, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109252,1 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 25 May '20

25 May '20

Change 109252,1 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/109252/1 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/463/

1 0

[CQ]: 109252,1 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 25 May '20

25 May '20

Change 109252,1 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/109252/1 For failed test results see: https://jenkins-staging.phx.ovirt.org/job/dummy-master_change-queue-tester/…

1 0

[JIRA] (OVIRT-2947) ovirt organization under quay.io
by Evgheni Dereveanchin (oVirt JIRA) 25 May '20

25 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2947?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2947: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > ovirt organization under quay.io > -------------------------------- > > Key: OVIRT-2947 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2947 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: Evgheni Dereveanchin > > I need to publish some ovirt images [1] [2] and I'm going to use Openshift > CI to publish the images for me. > My question is who owns it and what is the procedure to create new repos > under it. > Thanks, > Roy > [1] https://github.com/ovirt/csi-driver > [2] https://github.com/ovirt/cluster-api-provider-ovirt -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[JIRA] (OVIRT-2947) ovirt organization under quay.io
by Roy Golan (oVirt JIRA) 25 May '20

25 May '20

Roy Golan created OVIRT-2947: -------------------------------- Summary: ovirt organization under quay.io Key: OVIRT-2947 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2947 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra I need to publish some ovirt images [1] [2] and I'm going to use Openshift CI to publish the images for me. My question is who owns it and what is the procedure to create new repos under it. Thanks, Roy [1] https://github.com/ovirt/csi-driver [2] https://github.com/ovirt/cluster-api-provider-ovirt -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.3 - Build # 450 - Failure!
by Yedidyah Bar David 25 May '20

25 May '20

On Fri, May 22, 2020 at 6:42 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/450/ > Build Number: 450 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #450 > [hbraha] network: explicitly set the filter to None > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: 008_restart_he_vm.restart_he_vm > > Error Message: > could not parse JSON: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5768 (Thu May 21 23:39:31 2020)\nhost-id=1\nscore=3400\nvm_conf_refresh_time=5768 (Thu May 21 23:39:32 2020)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-suite-4-3-host-0.lago.local", "host-id": 1, "engine-status": {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "4f6a7bea", "local_conf_timestamp": 5768, "host-ts": 5768}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5767 (Thu May 21 23:39:31 2020)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=5768 (Thu May 21 23:39:32 2020)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-suite-4-3-host-1", "host-id": 2, "en Again output cut after 1024 bytes. Still not sure why, pushed this to try a few times: https://gerrit.ovirt.org/109243 Best regards, -- Didi

1 1

[JIRA] (OVIRT-2946) Fwd: [Infra-private] [GitHub] Deprecation Notice
by Anton Marchukov (oVirt JIRA) 25 May '20

25 May '20

Anton Marchukov created OVIRT-2946: -------------------------------------- Summary: Fwd: [Infra-private] [GitHub] Deprecation Notice Key: OVIRT-2946 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2946 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Is this triggered by the jenkins plugin that needs to be updated? ---------- Forwarded message --------- From: GitHub <noreply(a)github.com> Date: Sun, May 24, 2020 at 9:57 AM Subject: [Infra-private] [GitHub] Deprecation Notice To: STD-CI Bot <infra-private(a)ovirt.org> Hi @ovirt-infra, On May 24th, 2020 at 07:57 (UTC) you used a password to access an endpoint through the GitHub API using Java/1.8.0_191: https://api.github.com/organizations/18700703/members/github-actions[bot] Basic authentication using a password to the API is deprecated and will soon no longer work. Visit https://developer.github.com/changes/2020-02-14-deprecating-password-auth/ for more information around suggested workarounds and removal dates. Thanks, The GitHub Team _______________________________________________ Infra-private mailing list -- infra-private(a)ovirt.org To unsubscribe send an email to infra-private-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra-private@ovirt.org/message/34QKU… -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 35 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 May '20

25 May '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 35 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #35 [jenkins CI] Auto create ovirt-4.3 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.002_bootstrap_pytest.test_verify_engine_backup Error Message: AssertionError: False != True after 600 seconds Stack Trace: prefix = <ovirtlago.prefix.OvirtPrefix object at 0x7fe96d065d90> @order_by(_TEST_LIST) def test_verify_engine_backup(prefix): engine_vm = prefix.virt_env.engine_vm() engine_vm.ssh( [ 'mkdir', '/var/log/ost-engine-backup', ], ) api = prefix.virt_env.engine_vm().get_api_v4() engine = api.system_service() with test_utils.TestEvent(engine, [9024, 9025]): #backup started event, completed result = engine_vm.ssh( [ 'engine-backup', '--mode=backup', '--file=/var/log/ost-engine-backup/backup.tgz', '--log=/var/log/ost-engine-backup/log.txt', ], ) > assert result.code == 0, \ 'Failed to run engine-backup with code {0}. Output: {1}'.format(result.code, result.out) ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:1303: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python2.7/contextlib.py:35: in __exit__ self.gen.throw(type, value, traceback) ../basic-suite-master/test_utils/__init__.py:290: in TestEvent lambda: /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:286: in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:273: in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ func = <function <lambda> at 0x7fe96cec6848>, value = True, timeout = 600 allowed_exceptions = [], initial_wait = 0 def assert_equals_within( func, value, timeout, allowed_exceptions=None, initial_wait=10 ): allowed_exceptions = allowed_exceptions or [] with utils.EggTimer(timeout) as timer: while not timer.elapsed(): try: res = func() if res == value: return except Exception as exc: if _instance_of_any(exc, allowed_exceptions): time.sleep(3) continue LOGGER.exception("Unhandled exception in %s", func) raise if initial_wait == 0: time.sleep(3) else: time.sleep(initial_wait) initial_wait = 0 try: raise AssertionError( > '%s != %s after %s seconds' % (res, value, timeout) ) E AssertionError: False != True after 600 seconds /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:252: AssertionError

1 1

[CQ]: 109255, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109255, 2 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109256, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109256, 2 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109254, 2 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109254, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109253, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

[CQ]: 109253, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '20

25 May '20

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

1 0

oVirt infra daily report - unstable production jobs - 1201
by jenkins＠jenkins.phx.ovirt.org 25 May '20

25 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1201//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2945) modify the alert_old_patches script to post additional information when it sends emails
by Shlomi Zidmi (oVirt JIRA) 24 May '20

24 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2945?page=com.atlassian.jira.… ] Shlomi Zidmi reassigned OVIRT-2945: ----------------------------------- Assignee: Shlomi Zidmi (was: infra) > modify the alert_old_patches script to post additional information when it sends emails > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2945 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2945 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Shlomi Zidmi > Assignee: Shlomi Zidmi > Priority: Low > > Currently emails only contain URLs for the relevant patches. > It could be nice if the script would be able to also send the subject of each patch for example, or anything that can be useful for the reader. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[JIRA] (OVIRT-2945) modify the alert_old_patches script to post additional information when it sends emails
by Shlomi Zidmi (oVirt JIRA) 24 May '20

24 May '20

Shlomi Zidmi created OVIRT-2945: ----------------------------------- Summary: modify the alert_old_patches script to post additional information when it sends emails Key: OVIRT-2945 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2945 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Shlomi Zidmi Assignee: infra Priority: Low Currently emails only contain URLs for the relevant patches. It could be nice if the script would be able to also send the subject of each patch for example, or anything that can be useful for the reader. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[CQ]: 109241, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '20

24 May '20

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

1 0

[CQ]: 109241, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '20

24 May '20

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

1 0

[oVirt Jenkins] ovirt-release_4.2_build-artifacts-el7-x86_64 - Build # 1053 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 May '20

24 May '20

Project: https://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/ Build: https://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/… Build Number: 1053 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1053 [Sandro Bonazzola] automation: add v2 configuration ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1200
by jenkins＠jenkins.phx.ovirt.org 24 May '20

24 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1200//artifact/exported… Cheers, Jenkins

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 27 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 May '20

23 May '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/27/ Build Number: 27 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #27 [hbraha] network: explicitly set the filter to None ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 005_network_by_label.assign_labeled_network Error Message: False != True after 180 seconds 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/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/005_network_by_label.py", line 149, in assign_labeled_network host_service, LABELED_NET_NAME)) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 282, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_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) AssertionError: False != True after 180 seconds

1 1

oVirt infra daily report - unstable production jobs - 1199
by jenkins＠jenkins.phx.ovirt.org 23 May '20

23 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1199//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 109215, 4 (ovirt-node-ng-image) failed "ovirt-master" system tests
by oVirt Jenkins 22 May '20

22 May '20

Change 109215,4 (ovirt-node-ng-image) 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/109215/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23853/

1 0

[CQ]: 108955, 2 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 22 May '20

22 May '20

Change 108955,2 (ovirt-system-tests) 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/108955/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23851/

1 0

[CQ]: 108955,2 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 22 May '20

22 May '20

Change 108955,2 (ovirt-system-tests) 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/108955/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3455/

1 0

oVirt infra daily report - unstable production jobs - 1198
by jenkins＠jenkins.phx.ovirt.org 22 May '20

22 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1198//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2944) RE: [ftpcom] oVirt mirror out of sync
by Shlomi Zidmi (oVirt JIRA) 21 May '20

21 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2944?page=com.atlassian.jira.… ] Shlomi Zidmi reassigned OVIRT-2944: ----------------------------------- Assignee: Shlomi Zidmi (was: infra) > RE: [ftpcom] oVirt mirror out of sync > ------------------------------------- > > Key: OVIRT-2944 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2944 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Erwin Bronkhorst - Studenten Net Twente > Assignee: Shlomi Zidmi > > Hello Shlomi, hello infrastructure support team, > > We have recently noticed you are quite out of sync with mirroring oVirt content (last synced more than a year ago). > Thank you for bringing this issue to our attention. A while ago, we migrated to a new server and a new maintainer for the oVirt mirror, and something went definitely wrong in these processes. Sorry for the inconvenience. > I think the major issue is that the public key that you have added is not in use anymore by us. > Could you please replace the old key (for the mirror at ftp://ftp.snt.utwente.nl (Studenten Net Twente)) with this one? > ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDcEujUQ3DLIGiuOCg0ZlLqZhQY/uHFw2O9cMY6SrlG11tZ0oiwk6+x8dZsBN0kAN7zd1IIOo4+E0cMYUrkiwj6dzVc/oKY9RtTCOKhmqq1tnPxKSpOXY+CZxm7e63uVx8CpVjhj/lOMnfL3jzyBbNfURsSgY+6edSkDGzy3ptaXBDlrVI4F5+2rjKI3VgflshjUUZo1Di22snnZ5zoB8tT/Q8MBMjnMtQcPqjPL/VgfbgKwFfgLOnZtXzTnAjMK14IA5XLN9PCrPtEajRM8mtesqkYSMoZ1KqKPGwZspIijKrnoYNeKjkZxZAq9xijboj4GboHxsKRxckaw686qrfpPdPHNrgtKZZNxO5RB+/tgNLBM1l0g/9rEAN2Pvytg2Ifahk20oEodCzW1qsCBWl6+4NwV8iW87rgN+AgibNg/QmEd2SKNHAhOldEPFpHQqDRHo6ZJY5XbOEepK/ti3UOzV/mQ4u1PnKpZBoqWmM9MWBOEMZP7Ems4DHR5vdAvYs8TrzgTasoOe/MkFZ9FZ31XRL4loyPU9gid06ENA+Yc9xyRssUtjNsQfCNV+enSzbMBr4FvWmSoJNoVbQyi3tj13emflBqP+rROpeG7mgol+aP49z3RW56wOS0dhFqg8AXRyp1QLld/rJXzb3UH5l7WTXhX7DCuySezxhEyi1lGw== ftpcom(a)ftp.snt.utwente.nl > Then I will try to set-up our scripting in order to get the mirror in sync as soon as possible. > Kind regards, > Erwin Bronkhorst > FTPCom Studenten Net Twente > Van: Shlomi Zidmi <szidmi(a)redhat.com> > Verzonden: dinsdag 19 mei 2020 19:01 > Aan: ftpcom(a)snt.utwente.nl > Onderwerp: [ftpcom] oVirt mirror out of sync > Hello from the oVirt infrastructure team, > We have recently noticed you are quite out of sync with mirroring oVirt content (last synced more than a year ago). > If you are still interested in mirroring oVirt, please keep your mirror up to date with our public content. > Otherwise, please let us know and you will be removed from our mirror list: > https://www.ovirt.org/community/get-involved/repository-mirrors.html > Thanks, > Shlomi > ------------ > oVirt community -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

[JIRA] (OVIRT-2944) RE: [ftpcom] oVirt mirror out of sync
by Erwin Bronkhorst - Studenten Net Twente (oVirt JIRA) 21 May '20

21 May '20

Erwin Bronkhorst - Studenten Net Twente created OVIRT-2944: -------------------------------------------------------------- Summary: RE: [ftpcom] oVirt mirror out of sync Key: OVIRT-2944 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2944 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Erwin Bronkhorst - Studenten Net Twente Assignee: infra Hello Shlomi, hello infrastructure support team, > We have recently noticed you are quite out of sync with mirroring oVirt content (last synced more than a year ago). Thank you for bringing this issue to our attention. A while ago, we migrated to a new server and a new maintainer for the oVirt mirror, and something went definitely wrong in these processes. Sorry for the inconvenience. I think the major issue is that the public key that you have added is not in use anymore by us. Could you please replace the old key (for the mirror at ftp://ftp.snt.utwente.nl (Studenten Net Twente)) with this one? ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDcEujUQ3DLIGiuOCg0ZlLqZhQY/uHFw2O9cMY6SrlG11tZ0oiwk6+x8dZsBN0kAN7zd1IIOo4+E0cMYUrkiwj6dzVc/oKY9RtTCOKhmqq1tnPxKSpOXY+CZxm7e63uVx8CpVjhj/lOMnfL3jzyBbNfURsSgY+6edSkDGzy3ptaXBDlrVI4F5+2rjKI3VgflshjUUZo1Di22snnZ5zoB8tT/Q8MBMjnMtQcPqjPL/VgfbgKwFfgLOnZtXzTnAjMK14IA5XLN9PCrPtEajRM8mtesqkYSMoZ1KqKPGwZspIijKrnoYNeKjkZxZAq9xijboj4GboHxsKRxckaw686qrfpPdPHNrgtKZZNxO5RB+/tgNLBM1l0g/9rEAN2Pvytg2Ifahk20oEodCzW1qsCBWl6+4NwV8iW87rgN+AgibNg/QmEd2SKNHAhOldEPFpHQqDRHo6ZJY5XbOEepK/ti3UOzV/mQ4u1PnKpZBoqWmM9MWBOEMZP7Ems4DHR5vdAvYs8TrzgTasoOe/MkFZ9FZ31XRL4loyPU9gid06ENA+Yc9xyRssUtjNsQfCNV+enSzbMBr4FvWmSoJNoVbQyi3tj13emflBqP+rROpeG7mgol+aP49z3RW56wOS0dhFqg8AXRyp1QLld/rJXzb3UH5l7WTXhX7DCuySezxhEyi1lGw== ftpcom(a)ftp.snt.utwente.nl Then I will try to set-up our scripting in order to get the mirror in sync as soon as possible. Kind regards, Erwin Bronkhorst FTPCom Studenten Net Twente Van: Shlomi Zidmi <szidmi(a)redhat.com> Verzonden: dinsdag 19 mei 2020 19:01 Aan: ftpcom(a)snt.utwente.nl Onderwerp: [ftpcom] oVirt mirror out of sync Hello from the oVirt infrastructure team, We have recently noticed you are quite out of sync with mirroring oVirt content (last synced more than a year ago). If you are still interested in mirroring oVirt, please keep your mirror up to date with our public content. Otherwise, please let us know and you will be removed from our mirror list: https://www.ovirt.org/community/get-involved/repository-mirrors.html Thanks, Shlomi ------------ oVirt community -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127)

1 0

Build failed in Jenkins: system-mk_mirrors_index-yum #85415
by jenkins＠jenkins.phx.ovirt.org 21 May '20

21 May '20

See <https://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/85415/display/red…> Changes: ------------------------------------------ Started by upstream project "system-sync_mirrors-ovirt-master-copr-AdvancedVirtualization-el8-x86_64" build number 147 originally caused by: Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10 ERROR: Timeout after 10 minutes ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:909) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1131) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1167) at hudson.scm.SCM.checkout(SCM.java:505) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:569) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mirrors.phx.ovirt.org at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:998) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor933.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy90.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:907) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1131) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1167) at hudson.scm.SCM.checkout(SCM.java:505) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) ERROR: Error fetching remote repo 'origin'

1 1

oVirt infra daily report - unstable production jobs - 1197
by jenkins＠jenkins.phx.ovirt.org 21 May '20

21 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1197//artifact/exported… Cheers, Jenkins

1 0

oVirt 4.4.0 Release is now generally available
by Sandro Bonazzola 20 May '20

20 May '20

oVirt 4.4.0 Release is now generally available The oVirt Project is excited to announce the general availability of the oVirt 4.4.0 Release, as of May 20th, 2020 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Some of the features included in the oVirt 4.4.0 release require content that will be available in CentOS Linux 8.2 but cannot be tested on RHEL 8.2 yet due to some incompatibility in the openvswitch package that is shipped in CentOS Virt SIG, which requires rebuilding openvswitch on top of CentOS 8.2. The cluster switch type OVS is not implemented for CentOS 8 hosts. Please note that oVirt 4.4 only supports clusters and datacenters with compatibility version 4.2 and above. If clusters or datacenters are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See users mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Installation instructions For the engine: either use the oVirt appliance or install CentOS Linux 8 minimal by following these steps: - Install the CentOS Linux 8 image from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8…, selecting the minimal installation. - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. Update instructionsUpdate from oVirt 4.4 Release Candidate On the engine side and on CentOS hosts, you’ll need to switch from ovirt44-pre to ovirt44 repositories. In order to do so, you need to: 1. dnf remove ovirt-release44-pre 2. rm -f /etc/yum.repos.d/ovirt-4.4-pre-dependencies.repo 3. rm -f /etc/yum.repos.d/ovirt-4.4-pre.repo 4. dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm 5. dnf update On the engine side you’ll need to run engine-setup only if you were not already on the latest release candidate. On oVirt Node, you’ll need to upgrade with: 1. Move node to maintenance 2. dnf install https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ovirt-node-ng-imag… 3. Reboot 4. Activate the host Update from oVirt 4.3 oVirt 4.4 is available only for CentOS 8. In-place upgrades from previous installations, based on CentOS 7, are not possible. For the engine, use backup, and restore that into a new engine. Nodes will need to be reinstalled. A 4.4 engine can still manage existing 4.3 hosts, but you can’t add new ones. For a standalone engine, please refer to upgrade procedure at https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 If needed, run ovirt-engine-rename (see engine rename tool documentation at https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html ) When upgrading hosts: You need to upgrade one host at a time. 1. Turn host to maintenance. Virtual machines on that host should migrate automatically to a different host. 2. Remove it from the engine 3. Re-install it with el8 or oVirt Node as per installation instructions 4. Re-add the host to the engine Please note that you may see some issues live migrating VMs from el7 to el8. If you hit such a case, please turn off the vm on el7 host and get it started on the new el8 host in order to be able to move the next el7 host to maintenance. What’s new in oVirt 4.4.0 Release? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts. - Easier network management and configuration flexibility with NetworkManager. - VMs based on a more modern Q35 chipset with legacy SeaBIOS and UEFI firmware. - Support for direct passthrough of local host disks to VMs. - Live migration improvements for High Performance guests. - New Windows guest tools installer based on WiX framework now moved to VirtioWin project. - Dropped support for cluster level prior to 4.2. - Dropped API/SDK v3 support deprecated in past versions. - 4K block disk support only for file-based storage. iSCSI/FC storage do not support 4K disks yet. - You can export a VM to a data domain. - You can edit floating disks. - Ansible Runner (ansible-runner) is integrated within the engine, enabling more detailed monitoring of playbooks executed from the engine. - Adding and reinstalling hosts is now completely based on Ansible, replacing ovirt-host-deploy, which is not used anymore. - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * 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.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: [ovirt-devel] oVirt and Fedora
by Michal Skrivanek 20 May '20

20 May '20

> On 19 May 2020, at 14:06, Neal Gompa <ngompa13(a)gmail.com> wrote: > > On Mon, May 11, 2020 at 11:45 AM Michal Skrivanek > <michal.skrivanek(a)redhat.com> wrote: >> >> >> >>> On 11 May 2020, at 14:49, Neal Gompa <ngompa13(a)gmail.com> wrote: >>> >>> On Mon, May 11, 2020 at 8:32 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> >>>> On Mon, May 11, 2020 at 2:24 PM Neal Gompa <ngompa13(a)gmail.com> wrote: >>>>> >>>>> As far as the oVirt software keeping up with Fedora, the main problem here has always been that people aren't integrating their software into the distribution itself. >> >> it was never a good fit for oVirt to be part of other distributions. We had individual packages part of Fedora in history, but there are things which are hard to accept (like automatically enabling of installed services, UIDs), and overall it’s just too complex, we’re rather a distribution than a simple app on top of base OS. >> > > None of those things are hard to do in Fedora. They're incredibly easy > to do. I know this because I've gone through this process already > before. > > But fine, let's assume I consider this argument valid. Then there's > still no reason not to be continually providing support for Fedora as > an add-on, as you have before. the reason is mentioned in the original email, the lack of resources to keep actively supporting 3 different platforms. If you want to provide a helping hand and maintain Fedora infrastructure I don’t think anyone would object > >>>>> That's how everything can get tested together. And this comes back to the old bug about fixing vdsm so that it doesn't use /rhev, but instead something FHS-compliant (RHBZ#1369102). Once that is resolved, pretty much the entire stack can go into Fedora. And then you benefit from the Fedora community being able to use, test, and contribute to the oVirt project. As it stands, why would anyone do this for you when you don't even run on the cutting edge platform that feeds into Red Hat Enterprise Linux? >>>> >>>> This was actually fixed a long time ago. With this commit: >>>> https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a0… >>>> >>>> You can configure a compatible vdsm that does not use /rhev. >>>> >>>> Of course it is not backward compatible, for this we need much more >>>> work to support live migration >>>> between old and new vdsm using different data-center configurations. >>>> >>> >>> It'd probably be simpler to just *change* it to an FHS-compatible path >>> going forward with EL8 and Fedora and set up a migration path there, >>> but it's a bit late for that... :( >> >> It wouldn’t. We always support live migration across several versions (now it’s 4.2-4.4) and it needs to stay the same or youo have to go with arcane code to mangle it back and forth which gets a bit ugly when you consider suspend/resume, snapshots, etc >> > > Erk. At some point you need to bite the bullet though... it’s about capacity as well, it’s just a matter of someone writing a code which can handle the (long) transition period Thanks, michal

1 0