- Infra - oVirt List Archives

[CQ]: 94135, 2 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 532 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Sep '18

05 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/… Build Number: 532 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #532 [Anton Marchukov] Removed /root/fluentd from collected artifacts. ----------------- Failed Tests: ----------------- No tests ran.

1 7

[CQ]: 94138, 1 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

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

1 0

[JIRA] (OVIRT-2479) CQ Failure - Alot of ovirt-hosted-engine-setup messages.
by Ehud Yonasi (oVirt JIRA) 05 Sep '18

05 Sep '18

Ehud Yonasi created OVIRT-2479: ---------------------------------- Summary: CQ Failure - Alot of ovirt-hosted-engine-setup messages. Key: OVIRT-2479 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2479 Project: oVirt - virtualization made easy Issue Type: Outage Components: Change Queue, OST Reporter: Ehud Yonasi Assignee: infra Since 3rd september there were alot of changes coming out of the blue to CQ about ovirt-hosted-engine-setup. while investigating why it happened, I found out that the remote repo was deleted somehow and was restored. That restoration caused all the project patches all-at-once triggers hundreds of jobs in build-art + CQ. In order to recover from that situation i had to find the last patch of that project and asked for a re-merge (ci re-merge please). After that change and multiple runs of CQ it passed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

oVirt infra weekly meeting notes 05.09.2018
by Evgheni Dereveanchin 05 Sep '18

05 Sep '18

Hi everyone, Please find this week's infra updates below: PHX: - Testing gerrit migration to el7 OVIRT-2472 <https://ovirt-jira.atlassian.net/browse/OVIRT-2472> - Let’s Encrypt certificate renewal not configured on new nagios host OVIRT-2473 <https://ovirt-jira.atlassian.net/browse/OVIRT-2473> - Resources disk still slowly filling up due to ISOs - New VM for OSAS will be named carla.osci.io OVIRT-2455 <https://ovirt-jira.atlassian.net/browse/OVIRT-2455> - ovirt-srv04 filled up - need to add disk space monitoring Todo: - Move jira redirect to OSAS web server OVIRT-2476 <https://ovirt-jira.atlassian.net/browse/OVIRT-2476> - Discuss breaking up resources to two servers OVIRT-2477 <https://ovirt-jira.atlassian.net/browse/OVIRT-2477> -- Regards, Evgheni Dereveanchin

1 0

[JIRA] (OVIRT-2477) optimize storage of tested repos
by Barak Korren (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2477?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2477: -------------------------------- Epic Link: OVIRT-2344 > optimize storage of tested repos > -------------------------------- > > Key: OVIRT-2477 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2477 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Currently tested repos that are used by CI are stored on the same FS as released RPMs. > This has several downsides: > * a single large FS is harder to manage (tested consumes half of this space) > * a single vNIC is used by both external repo consumers and internal CI workloads > * CI-related repo update jobs induce disk load and consume extra memory > Some options to solve this: > * move tested to a separate webserver > * keep using resources.ovirt.org but mount a separate FS under /repos/ovirt/tested > * store tested in some kind of object store? > Opening a ticket to discuss our workflows and improvement options. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2477) optimize storage of tested repos
by Barak Korren (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2477?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2477: -------------------------------- Epic Link: OVIRT-2344 > optimize storage of tested repos > -------------------------------- > > Key: OVIRT-2477 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2477 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Currently tested repos that are used by CI are stored on the same FS as released RPMs. > This has several downsides: > * a single large FS is harder to manage (tested consumes half of this space) > * a single vNIC is used by both external repo consumers and internal CI workloads > * CI-related repo update jobs induce disk load and consume extra memory > Some options to solve this: > * move tested to a separate webserver > * keep using resources.ovirt.org but mount a separate FS under /repos/ovirt/tested > * store tested in some kind of object store? > Opening a ticket to discuss our workflows and improvement options. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2478) CQ Master Failure - oVirt engine missing packages
by Ehud Yonasi (oVirt JIRA) 05 Sep '18

05 Sep '18

Ehud Yonasi created OVIRT-2478: ---------------------------------- Summary: CQ Master Failure - oVirt engine missing packages Key: OVIRT-2478 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2478 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Ehud Yonasi Assignee: infra There were failures in installing ovirt-engine for missing packages: nimbus-jose-jwt json-smart Like this failure: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10113/console I've sent a patch to fix that to ost: https://gerrit.ovirt.org/#/c/94183/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2477) optimize storage of tested repos
by Evgheni Dereveanchin (oVirt JIRA) 05 Sep '18

05 Sep '18

Evgheni Dereveanchin created OVIRT-2477: ------------------------------------------- Summary: optimize storage of tested repos Key: OVIRT-2477 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2477 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low Currently tested repos that are used by CI are stored on the same FS as released RPMs. This has several downsides: * a single large FS is harder to manage (tested consumes half of this space) * a single vNIC is used by both external repo consumers and internal CI workloads * CI-related repo update jobs induce disk load and consume extra memory Some options to solve this: * move tested to a separate webserver * keep using resources.ovirt.org but mount a separate FS under /repos/ovirt/tested * store tested in some kind of object store? Opening a ticket to discuss our workflows and improvement options. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2476) move jira redirect vhost to OSAS
by Evgheni Dereveanchin (oVirt JIRA) 05 Sep '18

05 Sep '18

Evgheni Dereveanchin created OVIRT-2476: ------------------------------------------- Summary: move jira redirect vhost to OSAS Key: OVIRT-2476 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2476 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra The jira.ovirt.org -> ovirt-jira.atlassian.net redirect is handled by a virtualhost located on monitoring.ovirt.org for historical reasons. Now that OSAS has a dedicated web host we can easily move it there to avoid mixing server roles. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2475) Make whitelist repo configurable from the Jenkins level
by Barak Korren (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2475?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2475: ----------------------------------- Assignee: Barak Korren (was: infra) > Make whitelist repo configurable from the Jenkins level > ------------------------------------------------------- > > Key: OVIRT-2475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2475 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, Standard CI (Freestyle), Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > Not every Jenkins instance need to use the oVirt whitelist, we need to make that configurable at least on the instance level. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2475) Make whitelist repo configurable from the Jenkins level
by Barak Korren (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2475?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2475: -------------------------------- Issue Type: Improvement (was: Bug) > Make whitelist repo configurable from the Jenkins level > ------------------------------------------------------- > > Key: OVIRT-2475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2475 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, Standard CI (Freestyle), Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Not every Jenkins instance need to use the oVirt whitelist, we need to make that configurable at least on the instance level. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2475) Make whitelist repo configurable from the Jenkins level
by Barak Korren (oVirt JIRA) 05 Sep '18

05 Sep '18

Barak Korren created OVIRT-2475: ----------------------------------- Summary: Make whitelist repo configurable from the Jenkins level Key: OVIRT-2475 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2475 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Master, Standard CI (Freestyle), Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra Priority: Highest Not every Jenkins instance need to use the oVirt whitelist, we need to make that configurable at least on the instance level. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 543 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Sep '18

05 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/543/ Build Number: 543 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #543 [Milan Zamazal] Disable verify_backup_snapshot_removed for clusters < 4.2 [Sandro Bonazzola] system-tests: drop sbonazzo from notified list ----------------- Failed Tests: ----------------- 15 tests failed. FAILED: network-suite-4.2.tests.test_mac_pools.test_set_mac_pool_duplicate_macs_from_true_to_false_while_dup_exists Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_mac_pools.test_assign_vnic_with_full_mac_pool_capacity_fails Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_mac_pools.test_undo_preview_snapshot_when_mac_used_reassigns_a_new_mac Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_mac_pools.test_mac_pools_in_different_clusters_dont_overlap Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_mac_pools.test_restore_snapshot_with_an_used_mac_implicitly_assigns_new_mac Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_mac_pools.test_move_stateless_vm_mac_to_new_vm_fails Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_mac_pools.test_move_mac_to_new_vm Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_qos_configuration.test_setup_net_with_qos Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_required_network.test_required_network_host_non_operational Error Message: test setup failure Stack Trace: default_cluster = <lib.clusterlib.Cluster object at 0x7f55ccea3d10> system = <lib.system.SDKSystemRoot object at 0x7f55cf78d110> @pytest.fixture(scope='module') def cluster_hosts_up(default_cluster, system): cluster_host_ids = default_cluster.host_ids() cluster_hosts = [] for host_id in cluster_host_ids: host = hostlib.Host(system) host.import_by_id(host_id) > host.wait_for_up_status() network-suite-4.2/tests/test_required_network.py:56: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:41: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fd7590> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_unrestricted_display_network_name.test_run_vm_with_unrestricted_display_network_name Error Message: test setup failure Stack Trace: host_1 = <lib.hostlib.Host object at 0x7f55c8fa1190> @pytest.fixture(scope='session') def host_1_up(host_1): > _wait_for_host_install(host_1) network-suite-4.2/fixtures/host.py:59: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:41: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1190> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-1 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_vm_operations.test_live_vm_migration_using_dedicated_network Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.test_vm_operations.test_hot_linking_vnic Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.ovn-provider.test_ovn_provider.test_validate_ovn_provider_connectivity Error Message: SshException: Ssh command "ovs-vsctl add-port br-int net10_port1 -- set interface net10_port1 type=internal" exited with status code 127. Stderr: bash: ovs-vsctl: command not found Stack Trace: default_ovn_provider_client = <shade.openstackcloud.OpenStackCloud object at 0x7f55c9c5c190> host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> host_1 = <lib.hostlib.Host object at 0x7f55c8fa1190> def test_validate_ovn_provider_connectivity(default_ovn_provider_client, host_0, host_1): net10_port1 = default_ovn_provider_client.get_port(NETWORK10_PORT1_NAME) net11_port1 = default_ovn_provider_client.get_port(NETWORK11_PORT1_NAME) net14_port1 = default_ovn_provider_client.get_port(NETWORK14_PORT1_NAME) net10_subnet1 = default_ovn_provider_client.get_subnet( NETWORK10_SUBNET1_NAME) net11_subnet1 = default_ovn_provider_client.get_subnet( NETWORK11_SUBNET1_NAME) net14_subnet1 = default_ovn_provider_client.get_subnet( NETWORK14_SUBNET1_NAME) connections = ( (host_0, net10_port1, net10_subnet1,), (host_1, net11_port1, net11_subnet1,), (host_1, net14_port1, net14_subnet1,) ) with _create_namespaces(connections): > with _create_ovs_ports(connections): network-suite-4.2/tests/ovn-provider/test_ovn_provider.py:71: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python2.7/contextlib.py:17: in __enter__ return self.gen.next() network-suite-4.2/tests/ovn-provider/test_ovn_provider.py:193: in _create_ovs_ports _exec(host, _add_ovs_port_command(port.name)) network-suite-4.2/tests/ovn-provider/test_ovn_provider.py:206: in _exec ' && '.join(commands)) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ address = '192.168.201.2', password = '123456' command = 'ovs-vsctl add-port br-int net10_port1 -- set interface net10_port1 type=internal' username = 'root' def exec_command(address, password, command, username=DEFAULT_USER): """ Execute a ssh command on a host :param address: address of the endpoint :param password: the password :param command: command to be executed :param username: the username, root if not specified :returns stdout: the standard output of the command :raises exc: Exception: if the command returns a non-zero exit status Example: hostname = sshlib.exec_command('192.168.1.5', 'password', 'hostname') """ client = paramiko.SSHClient() client.set_missing_host_key_policy(paramiko.WarningPolicy()) client.connect(address, username=username, password=password) try: _, stdout, stderr = client.exec_command(command) status = stdout.channel.recv_exit_status() if status != 0: stderr_message = stderr.read() raise SshException('Ssh command "{command}" exited with status ' 'code {status}. Stderr: {stderr}' .format(command=command, status=status, > stderr=stderr_message)) E SshException: Ssh command "ovs-vsctl add-port br-int net10_port1 -- set interface net10_port1 type=internal" exited with status code 127. Stderr: bash: ovs-vsctl: command not found network-suite-4.2/lib/sshlib.py:52: SshException FAILED: network-suite-4.2.tests.ovn-provider.test_ovn_provider_integration_with_ovirt.test_connect_vm_to_external_network Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError FAILED: network-suite-4.2.tests.ovs.test_ovn_physnet.test_connect_vm_to_external_physnet Error Message: test setup failure Stack Trace: host_0 = <lib.hostlib.Host object at 0x7f55c8fa1090> @pytest.fixture(scope='session') def host_0_up(host_0): > _wait_for_host_install(host_0) network-suite-4.2/fixtures/host.py:44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ network-suite-4.2/fixtures/host.py:79: in _wait_for_host_install host.wait_for_up_status(timeout=15 * 60) network-suite-4.2/lib/hostlib.py:209: in wait_for_up_status timeout=timeout) network-suite-4.2/lib/syncutil.py:47: in sync if success_criteria(result): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <lib.hostlib.Host object at 0x7f55c8fa1090> host_status = <HostStatus.INSTALL_FAILED: 'install_failed'> def _host_up_status_success_criteria(self, host_status): if host_status == HostStatus.UP: return True if host_status in (HostStatus.NON_OPERATIONAL, HostStatus.INSTALL_FAILED): > raise HostStatusError('{} is {}'.format(self.name, host_status)) E HostStatusError: lago-network-suite-4-2-host-0 is install_failed network-suite-4.2/lib/hostlib.py:230: HostStatusError

1 6

[JIRA] (OVIRT-2469) CQ Failure: can't install ovirt-host
by Dafna Ron (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2469?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2469: ---------------------------------- [~eyonasi(a)redhat.com] is this failing on both master and 4.2 (I see in the mails that both 4.2 and master failures were given this issue as cause). > CQ Failure: can't install ovirt-host > ------------------------------------- > > Key: OVIRT-2469 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2469 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > yum install ovirt-host returns a package that does not exist under tested repo which is: > ovirt-imageio-common = 1.4.4-0.el7 > [~grosenth(a)redhat.com] is working on a fix to the reposync config file which will include that package. > 1) http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3035//artifact/b… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[oVirt CI] standard-enqueue - Build #16282 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Sep '18

05 Sep '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/16282/ Build Name: #16282 Build Description: Gerrit: 94164 - ovirt-engine-nodejs (4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/94164 - title: Bump Node.js version to 8.11.4 - project: ovirt-engine-nodejs - branch: master - author: Greg Sheremeta <gshereme(a)redhat.com>

1 0

[JIRA] (OVIRT-2469) CQ Failure: can't install ovirt-host
by Dafna Ron (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2469?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2469: ---------------------------------- [~grosenth(a)redhat.com] can you please give me a status on this? > CQ Failure: can't install ovirt-host > ------------------------------------- > > Key: OVIRT-2469 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2469 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > yum install ovirt-host returns a package that does not exist under tested repo which is: > ovirt-imageio-common = 1.4.4-0.el7 > [~grosenth(a)redhat.com] is working on a fix to the reposync config file which will include that package. > 1) http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3035//artifact/b… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2474) Avoid duplicated code for mock runner's shell cmd
by Daniel Belenky (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2474?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2474: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Avoid duplicated code for mock runner's shell cmd > ------------------------------------------------- > > Key: OVIRT-2474 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2474 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Instead of having to maintain duplicated code for the mock shell > command (which is actually what runs in mock), we should store it in a > variable. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2474) Avoid duplicated code for mock runner's shell cmd
by Daniel Belenky (oVirt JIRA) 05 Sep '18

05 Sep '18

Daniel Belenky created OVIRT-2474: ------------------------------------- Summary: Avoid duplicated code for mock runner's shell cmd Key: OVIRT-2474 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2474 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Daniel Belenky Assignee: infra Instead of having to maintain duplicated code for the mock shell command (which is actually what runs in mock), we should store it in a variable. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2469) CQ Failure: can't install ovirt-host
by Dafna Ron (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2469?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2469: ----------------------------- Issue Type: Bug (was: Outage) > CQ Failure: can't install ovirt-host > ------------------------------------- > > Key: OVIRT-2469 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2469 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > yum install ovirt-host returns a package that does not exist under tested repo which is: > ovirt-imageio-common = 1.4.4-0.el7 > [~grosenth(a)redhat.com] is working on a fix to the reposync config file which will include that package. > 1) http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3035//artifact/b… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 94107, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 94107,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 94081,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 94081,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/94107/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/94081/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10118/

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 445 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Sep '18

05 Sep '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/445/ Build Number: 445 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #445 [Milan Zamazal] Disable verify_backup_snapshot_removed for clusters < 4.2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Failed to read response: [(<pycurl.Curl object at 0x7fe75e2fe050>, 7, 'TCP connection reset by peer')] -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fe75e35d0c8> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37037, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait response = self._connection.wait(self._context) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait return self.__wait(context, failed_auth) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait raise Error("Failed to read response: {}".format(err_list)) Error: Failed to read response: [(<pycurl.Curl object at 0x7fe75e2fe050>, 7, 'TCP connection reset by peer')] --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 278, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37037, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait response = self._connection.wait(self._context) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait return self.__wait(context, failed_auth) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait raise Error("Failed to read response: {}".format(err_list)) 'Failed to read response: [(<pycurl.Curl object at 0x7fe75e2fe050>, 7, \'TCP connection reset by peer\')]\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fe75e35d0c8>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37037, in get\n return self._internal_get(headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait\n response = self._connection.wait(self._context)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait\n return self.__wait(context, failed_auth)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait\n raise Error("Failed to read response: {}".format(err_list))\nError: Failed to read response: [(<pycurl.Curl object at 0x7fe75e2fe050>, 7, \'TCP connection reset by peer\')]\n--------------------- >> end captured logging << ---------------------'

1 1

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

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 94119,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 94081,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 94081,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/94119/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/94081/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10114/

1 0

Jenkins account
by Steven Rosenberg 05 Sep '18

05 Sep '18

Dear Personnel, Please provide me with a Jenkins account so that I can log into Jenkins for my work. Thank you in advance for your help. With Best Regards. Steven Rosenberg.

2 2

[JIRA] (OVIRT-2473) fix let's encrypt renewal on monitoring.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 05 Sep '18

05 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2473?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2473: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > fix let's encrypt renewal on monitoring.ovirt.org > ------------------------------------------------- > > Key: OVIRT-2473 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2473 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Looks like Let's Encrypt renewal was not configured during migration done in OVIRT-502 > Certs are due to expire in a few weeks, opening ticket to set up renewal on the new host. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2473) fix let's encrypt renewal on monitoring.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 05 Sep '18

05 Sep '18

Evgheni Dereveanchin created OVIRT-2473: ------------------------------------------- Summary: fix let's encrypt renewal on monitoring.ovirt.org Key: OVIRT-2473 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2473 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Looks like Let's Encrypt renewal was not configured during migration done in OVIRT-502 Certs are due to expire in a few weeks, opening ticket to set up renewal on the new host. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 94161,1 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Sep '18

05 Sep '18

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

1 0

[CQ]: 94081,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 05 Sep '18

05 Sep '18

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1915
by jenkins＠jenkins.phx.ovirt.org 05 Sep '18

05 Sep '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 06f2258c4f26aafc38b771f28eb6e756a67974ea (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 06f2258c4f26aafc38b771f28eb6e756a67974ea Commit message: "stdci_runner: increase timeout to 3 hours" > git rev-list --no-walk 06f2258c4f26aafc38b771f28eb6e756a67974ea # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5804417533535354860.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 83057, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83057,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83057/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10104/

1 0

[CQ]: 83587, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83587,3 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83587/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10099/

1 0

[CQ]: 81712, 13 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 81712,13 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/81712/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10094/

1 0

[CQ]: 83027, 8 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83027,8 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83027/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10089/

1 0

[CQ]: 83148, 100 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83148,100 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83148/100 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10084/

1 0

[CQ]: 83869, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83869,3 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83869/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10079/

1 0

[CQ]: 83893, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83893,3 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83893/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10074/

1 0

[CQ]: 83895, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83895,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83895/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10069/

1 0

[CQ]: 83897, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83897,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83897/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10064/

1 0

[CQ]: 83899, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83899,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83899/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10059/

1 0

[CQ]: 83978, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83978,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83978/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10054/

1 0

[CQ]: 83989, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 83989,3 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83989/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10049/

1 0

[CQ]: 84024, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84024,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84024/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10044/

1 0

[CQ]: 84027, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84027,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84027/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10039/

1 0

[CQ]: 84036, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84036,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84036/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10033/

1 0

[CQ]: 84043, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84043,3 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84043/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10027/

1 0

[CQ]: 84110, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84110,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84110/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10021/

1 0

[CQ]: 84199, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84199,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84199/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10015/

1 0

[CQ]: 84152, 5 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84152,5 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84152/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10009/

1 0

[CQ]: 84232, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Sep '18

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84232,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84232/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10003/

1 0

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

05 Sep '18

A system test invoked by the "ovirt-master" change queue including change 84153,7 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86760,2 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86760,2 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84153/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86760/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9997/

1 0