May 2020 - Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_upgrade-from-prevrelease-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-prevrelease-s… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_upgrade-from-prevrelease-s… Build Number: 1 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

1 5

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_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-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/43/ 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_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