- Infra - oVirt List Archives

[Ovirt] [CQ weekly status] [29-03-2019]
by Dafna Ron 29 Mar '19

29 Mar '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) Last CQ job failure on 4.2 was 25-03-2019 on project ovirt-ansible-hosted-engine-setup due missing polkit package. *CQ-4.3*: RED (#1) failures in 4.3 and master this week were caused by two issues: 1. we have had random failures on 4 different tests which we are working on debugging with Marcin, Martin and several more people. this has been disruptive this week but did not cause any delays as I was re-triggering failed projects to insure they have their packages buit in tested. Currently we suspect api issue or changes to poastgres are causing the failures 2. we had libcgroup-tools package missing which cause failures for all projects in initialize engine. I merged a patch to fix the issue and provide the package. *CQ-Master:* RED (#1) We have had the same issues as in 4.3 this week. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[JIRA] (OVIRT-2711) Kernel soft lockup on vm0085.workers-phx.ovirt.org while building ovirt-node
by sbonazzo (oVirt JIRA) 29 Mar '19

29 Mar '19

sbonazzo created OVIRT-2711: ------------------------------- Summary: Kernel soft lockup on vm0085.workers-phx.ovirt.org while building ovirt-node Key: OVIRT-2711 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2711 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra *https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/151/console <https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-…>* *07:51:38* 06:51:37,952 EMERG kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [scsi_eh_1:85]*07:51:38* 06:51:37,952 WARNING kernel:Modules linked in: xfs fcoe libfcoe libfc scsi_transport_fc zram scsi_dh_rdac scsi_dh_emc scsi_dh_alua parport_pc i2c_piix4 parport joydev loop nls_utf8 isofs 8021q garp mrp stp llc virtio_console serio_raw qemu_fw_cfg virtio_pci e1000 bochs_drm drm_kms_helper ttm drm ata_generic pata_acpi sunrpc mcryptd sha256_ssse3 dm_crypt dm_round_robin dm_multipath linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 iscsi_ibft iscsi_boot_sysfs floppy iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs zstd_decompress xxhash cramfs edd virtio_rng virtio_ring virtio*07:51:38* 06:51:37,953 WARNING kernel:CPU: 0 PID: 85 Comm: scsi_eh_1 Not tainted 4.16.3-301.fc28.x86_64 #1*07:51:38* 06:51:37,954 WARNING kernel:Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20180531_142017-buildhw-08.phx2.fedoraproject.org-1.fc28 04/01/2014*07:51:38* 06:51:37,954 WARNING kernel:RIP: 0010:_raw_spin_unlock_irqrestore+0xd/0x20*07:51:38* 06:51:37,954 WARNING kernel:RSP: 0018:ffffa53b8048bdf0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff12*07:51:38* 06:51:37,954 WARNING kernel:RAX: 0000000000000000 RBX: ffff9898e8c58000 RCX: 0000000000000000*07:51:38* 06:51:37,955 WARNING kernel:RDX: 0000000000000000 RSI: 0000000000000202 RDI: 0000000000000202*07:51:38* 06:51:37,955 WARNING kernel:RBP: ffffffff9860bd20 R08: 0000000000000038 R09: 000000000000029e*07:51:38* 06:51:37,956 WARNING kernel:R10: 0000000000000000 R11: 0000000000000001 R12: ffffffff9860b050*07:51:38* 06:51:37,956 WARNING kernel:R13: ffff9898e8c58130 R14: 0000000000000202 R15: 0000000000000000*07:51:38* 06:51:37,957 WARNING kernel:FS: 0000000000000000(0000) GS:ffff9898fbc00000(0000) knlGS:0000000000000000*07:51:38* 06:51:37,957 WARNING kernel:CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033*07:51:38* 06:51:37,957 WARNING kernel:CR2: 00007f544a48d6d7 CR3: 0000000068dfc000 CR4: 00000000000006f0*07:51:38* 06:51:37,957 WARNING kernel:Call Trace:*07:51:38* 06:51:37,958 WARNING kernel: ata_sff_error_handler+0x83/0xe0*07:51:38* 06:51:37,958 WARNING kernel: ata_scsi_port_error_handler+0x354/0x770*07:51:38* 06:51:37,958 WARNING kernel: ? scsi_try_target_reset+0x90/0x90*07:51:38* 06:51:37,959 WARNING kernel: ? scsi_eh_get_sense+0x220/0x220*07:51:38* 06:51:37,959 WARNING kernel: ata_scsi_error+0x91/0xc0*07:51:38* 06:51:37,959 WARNING kernel: scsi_error_handler+0xd0/0x5b0*07:51:38* 06:51:37,959 WARNING kernel: ? __schedule+0x23f/0x850*07:51:38* 06:51:37,960 WARNING kernel: ? scsi_eh_get_sense+0x220/0x220*07:51:38* 06:51:37,960 WARNING kernel: kthread+0x112/0x130*07:51:38* 06:51:37,960 WARNING kernel: ? kthread_create_worker_on_cpu+0x70/0x70*07:51:38* 06:51:37,960 WARNING kernel: ? kthread_create_worker_on_cpu+0x70/0x70*07:51:38* 06:51:37,960 WARNING kernel: ret_from_fork+0x35/0x40*07:51:38* 06:51:37,961 WARNING kernel:Code: a8 08 74 0b 65 81 25 6f 2c 76 67 ff ff ff 7f 89 d0 c3 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 c6 07 00 48 89 f7 57 9d <0f> 1f 44 00 00 c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f Running yum check-update on the slave shows several updates available including kernel. I would recommend to upgrade slaves. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-5-el7-x86_64 #205
by jenkins＠jenkins.phx.ovirt.org 29 Mar '19

29 Mar '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/205…> ------------------------------------------ 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-glusterfs-5-el7-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision e2723ce1cb5307c98934c8f527598905fdf087ce (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e2723ce1cb5307c98934c8f527598905fdf087ce Commit message: "stdci_slaves: increase memory requirement" > git rev-list --no-walk e2723ce1cb5307c98934c8f527598905fdf087ce # timeout=10 [system-sync_mirrors-glusterfs-5-el7-x86_64] $ /bin/bash -xe /tmp/jenkins504825524289935617.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs glusterfs-5-el7 yum + local repo_name=glusterfs-5-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/glusterfs-5-el7 /var/www/html/repos/yum/glusterfs-5-el7/base + check_yum_sync_needed glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/glusterfs-5-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=glusterfs-5-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=glusterfs-5-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/glusterfs-5-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: glusterfs-5-el7: Check uncompressed DB failed + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 526 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Mar '19

29 Mar '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/526/ Build Number: 526 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #526 No changes ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.verify_add_all_hosts_42 Error Message: 1 hosts failed installation: lago-compat-4-2-suite-master-host-1: non_operational -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function <lambda> at 0x7f2597ab1488> 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_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 342, in <lambda> lambda: _all_hosts_up(hosts_service, total_hosts), File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 137, in _all_hosts_up _check_problematic_hosts(hosts_service) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 157, in _check_problematic_hosts raise RuntimeError(dump_hosts) RuntimeError: 1 hosts failed installation: lago-compat-4-2-suite-master-host-1: non_operational --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 343, in verify_add_all_hosts timeout=constants.ADD_HOST_TIMEOUT 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_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 342, in <lambda> lambda: _all_hosts_up(hosts_service, total_hosts), File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 137, in _all_hosts_up _check_problematic_hosts(hosts_service) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 157, in _check_problematic_hosts raise RuntimeError(dump_hosts) '1 hosts failed installation:\nlago-compat-4-2-suite-master-host-1: non_operational\n\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function <lambda> at 0x7f2597ab1488>\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_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 342, in <lambda>\n lambda: _all_hosts_up(hosts_service, total_hosts),\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 137, in _all_hosts_up\n _check_problematic_hosts(hosts_service)\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 157, in _check_problematic_hosts\n raise RuntimeError(dump_hosts)\nRuntimeError: 1 hosts failed installation:\nlago-compat-4-2-suite-master-host-1: non_operational\n\n--------------------- >> end captured logging << ---------------------'

1 1

oVirt infra daily report - unstable production jobs - 778
by jenkins＠jenkins.phx.ovirt.org 29 Mar '19

29 Mar '19

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

1 0

[CQ]: 99014, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[JIRA] (OVIRT-2705) Re: way to link my Github account with Gerrit?
by Evgheni Dereveanchin (oVirt JIRA) 28 Mar '19

28 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2705?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2705: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: way to link my Github account with Gerrit? > ---------------------------------------------- > > Key: OVIRT-2705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2705 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Evgheni Dereveanchin > > Hello Sahina. > Yes, we can merge those accounts. I am adding infra-support to make sure the ticket is opened on this. > Anton. > > On 22 Mar 2019, at 11:36, Sahina Bose <sabose(a)redhat.com> wrote: > > > > Hi, > > It looks like I ended up creating 2 different gerrit accounts. Is > > there a way to link the two? or delete one ? > > > > thanks > > sahina > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/F5QSCR42G5KQP… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98965, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 99008,1 (cockpit-ovirt) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 98945, 4 (ovirt-engine-metrics) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 98945, 4 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 98825, 13 (ovirt-engine-metrics) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 98959, 2 (ovirt-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 98825, 13 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 28 Mar '19

28 Mar '19

Change 98825,13 (ovirt-engine-metrics) 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/98825/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13603/

1 0

[CQ]: 98958, 1 (ovirt-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Mar '19

28 Mar '19

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

1 0

Build failed in Jenkins: deploy-to_ovirt-master_tested #6939
by jenkins＠jenkins.phx.ovirt.org 28 Mar '19

28 Mar '19

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/6939/display/red…> ------------------------------------------ Started by upstream project "ovirt-release_master_build-artifacts-el7-x86_64" build number 1071 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on vm0010.workers-phx.ovirt.org (el7 phx nested) in workspace <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/> [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-yD2vOxbmrcTR/agent.13062 SSH_AGENT_PID=13064 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/@tmp/private_…> (<http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/@tmp/private_…)> [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-master_tested] $ /bin/bash -xe /tmp/jenkins9084038950820629873.sh + [[ http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… == '' ]] + queue_name=ovirt-master + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org + echo repo-extra-dir:master + echo http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Pseudo-terminal will not be allocated because stdin is not a terminal. + BASE_DIR=/srv/resources/repos/ovirt/tested + PUBLISH_MD_COPIES=50 + main + local tmp_dir + mkdir -p /srv/resources/repos/ovirt/tested ++ mktemp -d /srv/resources/repos/ovirt/tested/.deploy.XXXXXXXXXX + tmp_dir=/srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 + trap 'rm -rf '\''/srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2'\''' EXIT HUP + echo 'Collecting packages' Collecting packages + collect_packages /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 + local repoman_dst=/srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 + repoman --temp-dir generate-in-repo --option main.allowed_repo_paths=/srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 --option main.on_empty_source=warn /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 add conf:stdin 2019-03-28 00:02:32,444::INFO::repoman.cmd:: 2019-03-28 00:02:32,445::INFO::repoman.cmd::Adding artifacts to the repo /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 2019-03-28 00:02:32,445::INFO::repoman.common.repo::Adding repo extra dir master 2019-03-28 00:02:32,449::INFO::repoman.common.stores.RPM::Loading repo /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2/master 2019-03-28 00:02:32,450::INFO::repoman.common.stores.RPM::Repo /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2/master loaded 2019-03-28 00:02:32,453::INFO::repoman.common.stores.iso::Loading repo /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2/master 2019-03-28 00:02:32,453::INFO::repoman.common.stores.iso::Repo /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2/master loaded 2019-03-28 00:02:32,471::INFO::repoman.common.repo::Resolving artifact source http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… 2019-03-28 00:02:32,665::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '457', 'content-type': 'text/html;charset=utf-8', 'date': 'Thu, 28 Mar 2019 00:02:32 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head resURL="/static/2816b579" data-rooturl="" data-resurl="/static/2816b579"><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/static/2816b579/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-03-28 00:02:34,722::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '457', 'content-type': 'text/html;charset=utf-8', 'date': 'Thu, 28 Mar 2019 00:02:34 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head resURL="/static/2816b579" data-rooturl="" data-resurl="/static/2816b579"><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/static/2816b579/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-03-28 00:02:36,775::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '457', 'content-type': 'text/html;charset=utf-8', 'date': 'Thu, 28 Mar 2019 00:02:36 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head resURL="/static/2816b579" data-rooturl="" data-resurl="/static/2816b579"><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/static/2816b579/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-03-28 00:02:38,828::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '457', 'content-type': 'text/html;charset=utf-8', 'date': 'Thu, 28 Mar 2019 00:02:38 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head resURL="/static/2816b579" data-rooturl="" data-resurl="/static/2816b579"><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/static/2816b579/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/static/2816b579/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-03-28 00:02:40,831::ERROR::repoman.cmd:: 2019-03-28 00:02:40,832::ERROR::repoman.cmd::Error while adding conf:stdin 2019-03-28 00:02:40,834::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2/.lago_tmp/tmpRwH4yQ/tmpTclvWx 2019-03-28 00:02:40,835::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2/.lago_tmp/tmpRwH4yQ + rm -rf /srv/resources/repos/ovirt/tested/.deploy.bOIm2LY7k2 Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 13064 killed; [ssh-agent] Stopped.

1 1

planned Jenkins restart
by Evgheni Dereveanchin 28 Mar '19

28 Mar '19

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is over. -- Regards, Evgheni Dereveanchin

1 1

oVirt infra daily report - unstable production jobs - 777
by jenkins＠jenkins.phx.ovirt.org 28 Mar '19

28 Mar '19

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

1 0

[CQ]: 98957, 1 (ovirt-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[CQ]: 98946, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

Change 98946,2 (ovirt-engine-metrics) 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/98946/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13597/

1 0

[CQ]: 98955,1 (ovirt-host) failed "ovirt-master" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[CQ]: 98956,1 (ovirt-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[CQ]: bd630b0 (ovirt-ansible-cluster-upgrade) failed "ovirt-master" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

Change bd630b0 (ovirt-ansible-cluster-upgrade) 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://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/bd630b0450464… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13589/

1 0

[CQ]: 98949,1 (imgbased) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #423
by jenkins＠jenkins.phx.ovirt.org 27 Mar '19

27 Mar '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/42…> Changes: [Ehud Yonasi] usrc.py - snap to tag d/s repo. ------------------------------------------ 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-fedora-base-fc29-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 49400038f3d71e3ec4a70bb9700def49def1c375 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 49400038f3d71e3ec4a70bb9700def49def1c375 # timeout=10 Commit message: "usrc.py - snap to tag d/s repo." > git rev-list --no-walk 22c5fd9fd8dc52f7e9c8a6603cc45fc36567c179 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins7666666144083059139.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet 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 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 185, in __init__ raise MetaLinkRepoErrorParseFail, "File %s does not exist" %filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml does not exist + reposync_out='Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64 error was File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml.tmp is not XML' Build step 'Execute shell' marked build as failure

1 1

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2322
by jenkins＠jenkins.phx.ovirt.org 27 Mar '19

27 Mar '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ 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-kvm-common-el7-x86_…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/59/95959/1:test --prune # timeout=10 > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2687933073917312624.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-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 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-base-fc29. Please verify its path and try again Build step 'Execute shell' marked build as failure

1 1

[CQ]: 98883,1 (ovirt-iso-uploader) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[JIRA] (OVIRT-2709) Please create new repositories on ovirt github for new Ansible role
by Eyal Edri (oVirt JIRA) 27 Mar '19

27 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2709?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2709: ---------------------------------- Created. I think you can probably assign someone from each team to have also admin rights on the org so you can do it as self-service as well and not have to wait for the team. Its straightforward to add new repos. Please reach out to the team once you need to setup a CI service for it. On Wed, Mar 27, 2019 at 2:07 PM Shirly Radco (oVirt JIRA) < -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Please create new repositories on ovirt github for new Ansible role > ------------------------------------------------------------------- > > Key: OVIRT-2709 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2709 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shirly Radco > Assignee: infra > > Please create following repositories: > ovirt-ansible-origin-on-ovirt > And please assign sradco, rgolan, machacekondra and mwperina as administrators. > Thanks. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2709) Please create new repositories on ovirt github for new Ansible role
by Shirly Radco (oVirt JIRA) 27 Mar '19

27 Mar '19

Shirly Radco created OVIRT-2709: ----------------------------------- Summary: Please create new repositories on ovirt github for new Ansible role Key: OVIRT-2709 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2709 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shirly Radco Assignee: infra Please create following repositories: ovirt-ansible-origin-on-ovirt And please assign sradco, rgolan, machacekondra and mwperina as administrators. Thanks. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

2 1

[CQ]: 98935,1 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[CQ]: 98658,6 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[CQ]: 0609480 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Mar '19

27 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change 0609480 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change c8bf2e0 (ovirt-ansible-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 c8bf2e0 (ovirt-ansible-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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/06094800d… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/c8bf2e0ee… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/428/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 521 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Mar '19

27 Mar '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/521/ Build Number: 521 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #521 [Milan Zamazal] Add hc-basic-suite-4.3 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.hotplug_cpu_42 Error Message: Timed out (in 309 s) trying to ssh to 192.168.202.149 -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:3cdb0e1f-249d-48b3-9756-9beed2a9fb58:Get ssh client for lago-compat-4-2-suite-master-host-1: lago.ssh: DEBUG: end task:3cdb0e1f-249d-48b3-9756-9beed2a9fb58:Get ssh client for lago-compat-4-2-suite-master-host-1: lago.ssh: DEBUG: Running d5bc0b52 on lago-compat-4-2-suite-master-host-1: host vm0 lago.ssh: DEBUG: Command d5bc0b52 on lago-compat-4-2-suite-master-host-1 returned with 0 lago.ssh: DEBUG: Command d5bc0b52 on lago-compat-4-2-suite-master-host-1 output: vm0.lago.local has address 192.168.202.149 lago.ssh: DEBUG: start task:2d17e884-fbd6-4694-a0b3-11d9ce0786ce:Get ssh client for 192.168.202.149: lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: timed out lago.ssh: DEBUG: Still got 99 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 98 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 97 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 96 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 95 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 94 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 93 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 92 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 91 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 90 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 89 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 88 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 87 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 86 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 85 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 84 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 83 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 82 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 81 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 80 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 79 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 78 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 77 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 76 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 75 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 74 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 73 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 72 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 71 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 70 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 69 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 68 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 67 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 66 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 65 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 64 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 63 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 62 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 61 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 60 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 59 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 58 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 57 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 56 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 55 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 54 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 53 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 52 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 51 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 50 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 49 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 48 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 47 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 46 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 45 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 44 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 43 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 42 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 41 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 40 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 39 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 38 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 37 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 36 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 35 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 34 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 33 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 32 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 31 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 30 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 29 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 28 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 27 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 26 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 25 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 24 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 23 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 22 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 21 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 20 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 19 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 18 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 17 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 16 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 15 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 14 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 13 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 12 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 11 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 10 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 9 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 8 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 7 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 6 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 5 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 4 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 3 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 2 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 1 tries for 192.168.202.149 lago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149 lago.ssh: DEBUG: Still got 0 tries for 192.168.202.149 root: ERROR: end task:2d17e884-fbd6-4694-a0b3-11d9ce0786ce:Get ssh client for 192.168.202.149: lago.ssh: DEBUG: File "/usr/lib/python2.7/site-packages/lago/ssh.py", line 388, in get_ssh_client (end_time - start_time, host_name) --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/004_basic_sanity.py", line 999, in hotplug_cpu ret = _vm_ssh(prefix, VM0_NAME, ['lscpu']) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/004_basic_sanity.py", line 116, in _vm_ssh tries=tries, File "/usr/lib/python2.7/site-packages/lago/ssh.py", line 46, in ssh password=password, File "/usr/lib/python2.7/site-packages/lago/ssh.py", line 388, in get_ssh_client (end_time - start_time, host_name) 'Timed out (in 309 s) trying to ssh to 192.168.202.149\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:3cdb0e1f-249d-48b3-9756-9beed2a9fb58:Get ssh client for lago-compat-4-2-suite-master-host-1:\nlago.ssh: DEBUG: end task:3cdb0e1f-249d-48b3-9756-9beed2a9fb58:Get ssh client for lago-compat-4-2-suite-master-host-1:\nlago.ssh: DEBUG: Running d5bc0b52 on lago-compat-4-2-suite-master-host-1: host vm0\nlago.ssh: DEBUG: Command d5bc0b52 on lago-compat-4-2-suite-master-host-1 returned with 0\nlago.ssh: DEBUG: Command d5bc0b52 on lago-compat-4-2-suite-master-host-1 output:\n vm0.lago.local has address 192.168.202.149\n\nlago.ssh: DEBUG: start task:2d17e884-fbd6-4694-a0b3-11d9ce0786ce:Get ssh client for 192.168.202.149:\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: timed out\nlago.ssh: DEBUG: Still got 99 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 98 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 97 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 96 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 95 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 94 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 93 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 92 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 91 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 90 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 89 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 88 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 87 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 86 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 85 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 84 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 83 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 82 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 81 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 80 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 79 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 78 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 77 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 76 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 75 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 74 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 73 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 72 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 71 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 70 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 69 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 68 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 67 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 66 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 65 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 64 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 63 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 62 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 61 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 60 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 59 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 58 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 57 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 56 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 55 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 54 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 53 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 52 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 51 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 50 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 49 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 48 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 47 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 46 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 45 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 44 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 43 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 42 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 41 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 40 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 39 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 38 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 37 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 36 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 35 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 34 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 33 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 32 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 31 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 30 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 29 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 28 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 27 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 26 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 25 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 24 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 23 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 22 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 21 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 20 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 19 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 18 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 17 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 16 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 15 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 14 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 13 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 12 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 11 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 10 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 9 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 8 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 7 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 6 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 5 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 4 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 3 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 2 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 1 tries for 192.168.202.149\nlago.ssh: DEBUG: Socket error connecting to 192.168.202.149: [Errno None] Unable to connect to port 22 on 192.168.202.149\nlago.ssh: DEBUG: Still got 0 tries for 192.168.202.149\nroot: ERROR: end task:2d17e884-fbd6-4694-a0b3-11d9ce0786ce:Get ssh client for 192.168.202.149:\nlago.ssh: DEBUG: File "/usr/lib/python2.7/site-packages/lago/ssh.py", line 388, in get_ssh_client\n (end_time - start_time, host_name)\n\n--------------------- >> end captured logging << ---------------------'

1 4

[CQ]: 98918, 1 (ovirt-engine-api-model) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

[CQ]: c8bf2e0 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

Change c8bf2e0 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/c8bf2e0ee… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/423/

1 0

[CQ]: 5c33604 (v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

Change 5c33604 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/5c33604a5abb9f138064932… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13581/

1 0

[CQ]: 98891, 3 (ovirt-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Mar '19

27 Mar '19

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

1 0

oVirt infra daily report - unstable production jobs - 776
by jenkins＠jenkins.phx.ovirt.org 27 Mar '19

27 Mar '19

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

1 0

[CQ]: 98887, 1 (ovirt-log-collector) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Mar '19

26 Mar '19

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

1 0

[CQ]: 0609480 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 26 Mar '19

26 Mar '19

Change 0609480 (ovirt-ansible-hosted-engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/06094800d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13579/

1 0

[CQ]: 98883,1 (ovirt-iso-uploader) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Mar '19

26 Mar '19

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

1 0

[CQ]: 98918, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Mar '19

26 Mar '19

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

1 0

[CQ]: 98865,3 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Mar '19

26 Mar '19

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

1 0

[CQ]: 95636,14 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 26 Mar '19

26 Mar '19

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

1 0

[JIRA] (OVIRT-2586) Memory leak in Jenkins SSE Gateway plugin
by Eyal Edri (oVirt JIRA) 26 Mar '19

26 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2586: ---------------------------------- Good news! How do you run it on a daily basis? do you plan to add a jenkins job or cronjob ? > Memory leak in Jenkins SSE Gateway plugin > ----------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Attachments: usedMemory_year.png > > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98886,1 (ovirt-log-collector) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Mar '19

26 Mar '19

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

2 1

[JIRA] (OVIRT-2705) Re: way to link my Github account with Gerrit?
by sabose (oVirt JIRA) 26 Mar '19

26 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2705?page=com.atlassian.jira.… ] sabose commented on OVIRT-2705: ------------------------------- Yes, I see that it now all linked. Thanks very much. On Tue, Mar 26, 2019 at 6:51 PM Evgheni Dereveanchin (oVirt JIRA) < > Re: way to link my Github account with Gerrit? > ---------------------------------------------- > > Key: OVIRT-2705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2705 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Evgheni Dereveanchin > > Hello Sahina. > Yes, we can merge those accounts. I am adding infra-support to make sure the ticket is opened on this. > Anton. > > On 22 Mar 2019, at 11:36, Sahina Bose <sabose(a)redhat.com> wrote: > > > > Hi, > > It looks like I ended up creating 2 different gerrit accounts. Is > > there a way to link the two? or delete one ? > > > > thanks > > sahina > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/F5QSCR42G5KQP… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2705) Re: way to link my Github account with Gerrit?
by Evgheni Dereveanchin (oVirt JIRA) 26 Mar '19

26 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2705?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2705: --------------------------------------------- I've actually found three different accounts so merged them as one. Sahina, could you please confirm you can log in via github to the main account? > Re: way to link my Github account with Gerrit? > ---------------------------------------------- > > Key: OVIRT-2705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2705 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Evgheni Dereveanchin > > Hello Sahina. > Yes, we can merge those accounts. I am adding infra-support to make sure the ticket is opened on this. > Anton. > > On 22 Mar 2019, at 11:36, Sahina Bose <sabose(a)redhat.com> wrote: > > > > Hi, > > It looks like I ended up creating 2 different gerrit accounts. Is > > there a way to link the two? or delete one ? > > > > thanks > > sahina > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/F5QSCR42G5KQP… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JENKINS] Failed to setup proejct ovirt-engine-metrics_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Mar '19

26 Mar '19

Failed to run project_setup.sh for: #315 ovirt-engine-metrics [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0087.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2586) Memory leak in Jenkins SSE Gateway plugin
by Evgheni Dereveanchin (oVirt JIRA) 26 Mar '19

26 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2586: --------------------------------------------- Jenkins was hit by the issue again today with 15800 MB used out of 16384 so I tried the workaround script attached to the upstream ticket. That helped drop memory usage to just 3532 MB which is very good news. We can install it to run on a daily basis to keep our Jenkins stable while the plugin is still not patched. > Memory leak in Jenkins SSE Gateway plugin > ----------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Attachments: usedMemory_year.png > > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0