- Infra - oVirt List Archives

Heads up! Influence of our recent Mock/Proxy changes on Lago jobs
by Barak Korren 23 Dec '16

23 Dec '16

Hi infra team members! As you may know, we've recently changed out proxied Mock configuration so that the 'http_proxy' environment variable gets defined inside the Mock environment. This was in an effort to make 'pip', 'curl' and 'wget' commands go through our PHX proxy. As it turns out, this also have unforeseen influence on yum tools. Now, when it come to yum, as it is used inside the mock environmet, we long has the proxied configuration hard-wiring it to use the proxy by setting it in "yum.conf". However, so far, yum tools (Such as reposync) that brought their own configuration, essentially bypassed the "yum.conf" file and hence were not using the proxy. Well, now it turns out that 'yum' and the derived tools also respect the 'http_proxy' environment variable [1]: 10.2. Configuring Proxy Server Access for a Single User To enable proxy access for a specific user, add the lines in the example box below to the user's shell profile. For the default bash shell, the profile is the file ~/.bash_profile. The settings below enable yum to use the proxy server mycache.mydomain.com, connecting to port 3128. # The Web proxy server used by this account http_proxy="http://mycache.mydomain.com:3128" export http_proxy This is generally a good thing, but it can lead to formerly unexpected consequences. Case-to-point: The Lago job reposync failures of last Thursday (Dec 22nd, 2016). The root-cause behind the failures was that the "ovirt-web-ui-0.1.0-4.el7.centos.x86_64.rpm" file was changed in the "ovirt-master-snapshot-static" repo. Updating an RPM file without changing the version or revision numbers breaks YUM`s rules and makes reposync choke. We already knew about this and actually had a work-around in the Lago code [2]. We I came in Thursday morning, and saw reposync failing in all the Lago jobs, I just assumed that our work-around simply failed to work. My assumption was enforced by the fact that I was able to reproduce the issue by running 'reposync' manually on the Lago hosts, and also managed to rectify it by removing the offending from file the reposync cache. I spent the next few hours chasing down failing jobs and cleaning up the caches on the hosts they ran on. I took me a while to figure out that I was seeing the problem (Essentially, the older version of the package file) reappear on the same hosts over and over again! Wondering how could that be, and after ensuring the older package file was nowhere to be found on any of the repos the jobs were using, Me and Gal took a look at the Lago code to see if it could be causing the issue. Imagine our puzzlement when we realized the work-around code was doing _exactly_ what I was doing manually, and still somehow managed to make the very issue it was designed to solve reappear! Eventually the problem seemed to disappear on its own. Now, armed with the knowledge above I can provide a plausible explanation to what we were seeing. The difference between my manual executions of 'reposync' and the way Lago was running it was that Lago was running within Mock, where 'http_proxy' was defined. What was probably happening is that reposync kept getting the old RPM file from the proxy while still getting a newer yum metadate file. Conclusion - The next time such an issue arises, we must make sure to clear the PHX proxy cache, there is actually no need to clear the cache on the Lago hosts themselves, because our work-around will resolve the issue there. Longer term we may configure the proxy to not cache files coming from resources.ovirt.org. [1]: https://www.centos.org/docs/5/html/yum/sn-yum-proxy-server.html [2]: https://github.com/lago-project/lago/blob/master/ovirtlago/reposetup.py#L14… -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 3

Build failed in Jenkins: ovirt_3.6_he-system-tests #785
by jenkins＠jenkins.phx.ovirt.org 23 Dec '16

23 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/785/changes> Changes: [Yaniv Kaul] Fixes and changes to storage tests [Sandro Bonazzola] ovirt-appliance: exclude f23 node builders [Eyal Edri] remove fc23 slaves for lago testing [Yaniv Bronhaim] Add new vdsm branch ovirt-4.1 to automation checks [Eyal Edri] std ci: add notification plugin to standard CI [Sandro Bonazzola] ovirt-appliance: add check and manual jobs [Eyal Edri] adding missing vdsm builds for ppc64le [Ryan Barry] Add builders for ovirt-engine-appliance:ovirt-4.1-snapshot ------------------------------------------ [...truncated 931 lines...] >From 192.168.200.4 icmp_seq=99 Destination Host Unreachable >From 192.168.200.4 icmp_seq=100 Destination Host Unreachable >From 192.168.200.4 icmp_seq=101 Destination Host Unreachable >From 192.168.200.4 icmp_seq=102 Destination Host Unreachable >From 192.168.200.4 icmp_seq=103 Destination Host Unreachable >From 192.168.200.4 icmp_seq=104 Destination Host Unreachable 64 bytes from 192.168.200.99: icmp_seq=105 ttl=64 time=1.06 ms 64 bytes from 192.168.200.99: icmp_seq=106 ttl=64 time=0.769 ms 64 bytes from 192.168.200.99: icmp_seq=107 ttl=64 time=0.653 ms 64 bytes from 192.168.200.99: icmp_seq=108 ttl=64 time=0.684 ms 64 bytes from 192.168.200.99: icmp_seq=109 ttl=64 time=5.17 ms 64 bytes from 192.168.200.99: icmp_seq=110 ttl=64 time=1.70 ms 64 bytes from 192.168.200.99: icmp_seq=111 ttl=64 time=8.15 ms 64 bytes from 192.168.200.99: icmp_seq=112 ttl=64 time=0.762 ms 64 bytes from 192.168.200.99: icmp_seq=113 ttl=64 time=0.487 ms 64 bytes from 192.168.200.99: icmp_seq=114 ttl=64 time=0.901 ms 64 bytes from 192.168.200.99: icmp_seq=115 ttl=64 time=0.565 ms 64 bytes from 192.168.200.99: icmp_seq=116 ttl=64 time=7.10 ms 64 bytes from 192.168.200.99: icmp_seq=117 ttl=64 time=3.13 ms 64 bytes from 192.168.200.99: icmp_seq=118 ttl=64 time=7.50 ms 64 bytes from 192.168.200.99: icmp_seq=119 ttl=64 time=7.82 ms 64 bytes from 192.168.200.99: icmp_seq=120 ttl=64 time=3.79 ms 64 bytes from 192.168.200.99: icmp_seq=121 ttl=64 time=2.57 ms 64 bytes from 192.168.200.99: icmp_seq=122 ttl=64 time=8.06 ms 64 bytes from 192.168.200.99: icmp_seq=123 ttl=64 time=7.76 ms 64 bytes from 192.168.200.99: icmp_seq=124 ttl=64 time=12.8 ms 64 bytes from 192.168.200.99: icmp_seq=125 ttl=64 time=0.477 ms 64 bytes from 192.168.200.99: icmp_seq=126 ttl=64 time=7.97 ms 64 bytes from 192.168.200.99: icmp_seq=127 ttl=64 time=7.85 ms 64 bytes from 192.168.200.99: icmp_seq=128 ttl=64 time=0.735 ms 64 bytes from 192.168.200.99: icmp_seq=129 ttl=64 time=0.582 ms 64 bytes from 192.168.200.99: icmp_seq=130 ttl=64 time=4.02 ms 64 bytes from 192.168.200.99: icmp_seq=131 ttl=64 time=0.517 ms 64 bytes from 192.168.200.99: icmp_seq=132 ttl=64 time=11.0 ms 64 bytes from 192.168.200.99: icmp_seq=133 ttl=64 time=7.82 ms 64 bytes from 192.168.200.99: icmp_seq=134 ttl=64 time=8.90 ms 64 bytes from 192.168.200.99: icmp_seq=135 ttl=64 time=0.706 ms 64 bytes from 192.168.200.99: icmp_seq=136 ttl=64 time=4.23 ms 64 bytes from 192.168.200.99: icmp_seq=137 ttl=64 time=7.23 ms 64 bytes from 192.168.200.99: icmp_seq=138 ttl=64 time=0.562 ms 64 bytes from 192.168.200.99: icmp_seq=139 ttl=64 time=22.0 ms 64 bytes from 192.168.200.99: icmp_seq=140 ttl=64 time=7.85 ms 64 bytes from 192.168.200.99: icmp_seq=141 ttl=64 time=7.83 ms 64 bytes from 192.168.200.99: icmp_seq=142 ttl=64 time=1.08 ms 64 bytes from 192.168.200.99: icmp_seq=143 ttl=64 time=1.19 ms 64 bytes from 192.168.200.99: icmp_seq=144 ttl=64 time=0.712 ms 64 bytes from 192.168.200.99: icmp_seq=145 ttl=64 time=0.771 ms 64 bytes from 192.168.200.99: icmp_seq=146 ttl=64 time=0.738 ms 64 bytes from 192.168.200.99: icmp_seq=147 ttl=64 time=0.769 ms 64 bytes from 192.168.200.99: icmp_seq=148 ttl=64 time=8.01 ms 64 bytes from 192.168.200.99: icmp_seq=149 ttl=64 time=1.02 ms 64 bytes from 192.168.200.99: icmp_seq=150 ttl=64 time=0.808 ms 64 bytes from 192.168.200.99: icmp_seq=151 ttl=64 time=0.788 ms 64 bytes from 192.168.200.99: icmp_seq=152 ttl=64 time=0.848 ms 64 bytes from 192.168.200.99: icmp_seq=153 ttl=64 time=0.789 ms 64 bytes from 192.168.200.99: icmp_seq=154 ttl=64 time=0.861 ms 64 bytes from 192.168.200.99: icmp_seq=155 ttl=64 time=0.776 ms 64 bytes from 192.168.200.99: icmp_seq=156 ttl=64 time=2.93 ms 64 bytes from 192.168.200.99: icmp_seq=157 ttl=64 time=0.854 ms 64 bytes from 192.168.200.99: icmp_seq=158 ttl=64 time=0.655 ms 64 bytes from 192.168.200.99: icmp_seq=159 ttl=64 time=0.769 ms 64 bytes from 192.168.200.99: icmp_seq=160 ttl=64 time=0.927 ms 64 bytes from 192.168.200.99: icmp_seq=161 ttl=64 time=0.797 ms 64 bytes from 192.168.200.99: icmp_seq=162 ttl=64 time=0.757 ms 64 bytes from 192.168.200.99: icmp_seq=163 ttl=64 time=0.797 ms 64 bytes from 192.168.200.99: icmp_seq=164 ttl=64 time=0.835 ms 64 bytes from 192.168.200.99: icmp_seq=165 ttl=64 time=0.899 ms 64 bytes from 192.168.200.99: icmp_seq=166 ttl=64 time=0.802 ms 64 bytes from 192.168.200.99: icmp_seq=167 ttl=64 time=0.898 ms 64 bytes from 192.168.200.99: icmp_seq=168 ttl=64 time=0.839 ms 64 bytes from 192.168.200.99: icmp_seq=169 ttl=64 time=1.20 ms 64 bytes from 192.168.200.99: icmp_seq=170 ttl=64 time=0.718 ms 64 bytes from 192.168.200.99: icmp_seq=171 ttl=64 time=0.780 ms 64 bytes from 192.168.200.99: icmp_seq=172 ttl=64 time=0.715 ms 64 bytes from 192.168.200.99: icmp_seq=173 ttl=64 time=0.716 ms 64 bytes from 192.168.200.99: icmp_seq=174 ttl=64 time=0.694 ms 64 bytes from 192.168.200.99: icmp_seq=175 ttl=64 time=0.618 ms 64 bytes from 192.168.200.99: icmp_seq=176 ttl=64 time=0.689 ms 64 bytes from 192.168.200.99: icmp_seq=177 ttl=64 time=0.675 ms 64 bytes from 192.168.200.99: icmp_seq=178 ttl=64 time=0.692 ms 64 bytes from 192.168.200.99: icmp_seq=179 ttl=64 time=0.868 ms 64 bytes from 192.168.200.99: icmp_seq=180 ttl=64 time=0.726 ms 64 bytes from 192.168.200.99: icmp_seq=181 ttl=64 time=0.659 ms 64 bytes from 192.168.200.99: icmp_seq=182 ttl=64 time=0.698 ms 64 bytes from 192.168.200.99: icmp_seq=183 ttl=64 time=0.795 ms 64 bytes from 192.168.200.99: icmp_seq=184 ttl=64 time=0.893 ms 64 bytes from 192.168.200.99: icmp_seq=185 ttl=64 time=0.785 ms 64 bytes from 192.168.200.99: icmp_seq=186 ttl=64 time=0.824 ms 64 bytes from 192.168.200.99: icmp_seq=187 ttl=64 time=0.740 ms 64 bytes from 192.168.200.99: icmp_seq=188 ttl=64 time=0.740 ms 64 bytes from 192.168.200.99: icmp_seq=189 ttl=64 time=0.781 ms 64 bytes from 192.168.200.99: icmp_seq=190 ttl=64 time=0.767 ms 64 bytes from 192.168.200.99: icmp_seq=191 ttl=64 time=0.719 ms 64 bytes from 192.168.200.99: icmp_seq=192 ttl=64 time=0.632 ms 64 bytes from 192.168.200.99: icmp_seq=193 ttl=64 time=0.731 ms 64 bytes from 192.168.200.99: icmp_seq=194 ttl=64 time=0.606 ms 64 bytes from 192.168.200.99: icmp_seq=195 ttl=64 time=0.608 ms 64 bytes from 192.168.200.99: icmp_seq=196 ttl=64 time=0.545 ms 64 bytes from 192.168.200.99: icmp_seq=197 ttl=64 time=0.658 ms 64 bytes from 192.168.200.99: icmp_seq=198 ttl=64 time=0.625 ms 64 bytes from 192.168.200.99: icmp_seq=199 ttl=64 time=0.566 ms 64 bytes from 192.168.200.99: icmp_seq=200 ttl=64 time=0.676 ms 64 bytes from 192.168.200.99: icmp_seq=201 ttl=64 time=2.42 ms 64 bytes from 192.168.200.99: icmp_seq=202 ttl=64 time=0.624 ms 64 bytes from 192.168.200.99: icmp_seq=203 ttl=64 time=0.532 ms 64 bytes from 192.168.200.99: icmp_seq=204 ttl=64 time=0.581 ms 64 bytes from 192.168.200.99: icmp_seq=205 ttl=64 time=0.708 ms 64 bytes from 192.168.200.99: icmp_seq=206 ttl=64 time=0.582 ms 64 bytes from 192.168.200.99: icmp_seq=207 ttl=64 time=0.694 ms 64 bytes from 192.168.200.99: icmp_seq=208 ttl=64 time=0.737 ms 64 bytes from 192.168.200.99: icmp_seq=209 ttl=64 time=0.560 ms 64 bytes from 192.168.200.99: icmp_seq=210 ttl=64 time=0.549 ms 64 bytes from 192.168.200.99: icmp_seq=211 ttl=64 time=0.745 ms 64 bytes from 192.168.200.99: icmp_seq=212 ttl=64 time=0.660 ms 64 bytes from 192.168.200.99: icmp_seq=213 ttl=64 time=0.735 ms 64 bytes from 192.168.200.99: icmp_seq=214 ttl=64 time=0.556 ms 64 bytes from 192.168.200.99: icmp_seq=215 ttl=64 time=0.703 ms 64 bytes from 192.168.200.99: icmp_seq=216 ttl=64 time=0.666 ms 64 bytes from 192.168.200.99: icmp_seq=217 ttl=64 time=0.696 ms 64 bytes from 192.168.200.99: icmp_seq=218 ttl=64 time=0.762 ms 64 bytes from 192.168.200.99: icmp_seq=219 ttl=64 time=0.616 ms 64 bytes from 192.168.200.99: icmp_seq=220 ttl=64 time=0.628 ms --- 192.168.200.99 ping statistics --- 220 packets transmitted, 116 received, +104 errors, 47% packet loss, time 219089ms rtt min/avg/max/mdev = 0.477/2.170/22.036/3.284 ms, pipe 4 Warning: Permanently added '192.168.200.99' (ECDSA) to the list of known hosts. /var/tmp: 30 GiB (32196378624 bytes) trimmed [ INFO ] Stage: Initializing [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: ['/root/hosted-engine-deploy-answers-file.conf'] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161222222459-9yovu9.log Version: otopi-1.4.3_master (otopi-1.4.3-0.0.master.20160525142447.gitcf9c977.el7) [ INFO ] Hardware supports virtualization [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Generating libvirt-spice certificates [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. [ INFO ] Installing on additional host --== SYSTEM CONFIGURATION ==-- [WARNING] A configuration file must be supplied to deploy Hosted Engine on an additional host. [ INFO ] Answer file successfully loaded --== NETWORK CONFIGURATION ==-- [ INFO ] Additional host deployment, firewall manager is 'iptables' The following CPU types are supported by this host: - model_Haswell-noTSX: Intel Haswell-noTSX Family - model_SandyBridge: Intel SandyBridge Family - model_Westmere: Intel Westmere Family - model_Nehalem: Intel Nehalem Family - model_Penryn: Intel Penryn Family - model_Conroe: Intel Conroe Family --== HOSTED ENGINE CONFIGURATION ==-- [ INFO ] Stage: Setup validation [WARNING] Failed to resolve lago-he-basic-suite-3-6-host1.lago.local using DNS, it can be resolved only locally --== CONFIGURATION PREVIEW ==-- Engine FQDN : hosted-engine.lago.local Bridge name : ovirtmgmt Host address : lago-he-basic-suite-3-6-host1.lago.local SSH daemon port : 22 Firewall manager : iptables Gateway address : 192.168.200.1 Host name for web application : lago-he-basic-suite-3-6-host1 Storage Domain type : nfs3 Host ID : 2 Image size GB : 10 GlusterFS Share Name : hosted_engine_glusterfs GlusterFS Brick Provisioning : False Storage connection : lago-he-basic-suite-3-6-storage:/exports/nfs_he Console type : vnc Memory size MB : 3171 MAC address : 00:16:3e:24:d3:63 Boot type : disk Number of CPUs : 2 Restart engine VM after engine-setup: True CPU Type : model_SandyBridge [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Configuring libvirt [ INFO ] Configuring VDSM [ INFO ] Starting vdsmd [ INFO ] Waiting for VDSM hardware info [ INFO ] Configuring VM [ INFO ] Updating hosted-engine configuration [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Acquiring internal CA cert from the engine [ INFO ] The following CA certificate is going to be used, please immediately interrupt if not correct: [ INFO ] Issuer: C=US, O=lago.local, CN=hosted-engine.lago.local.54217, Subject: C=US, O=lago.local, CN=hosted-engine.lago.local.54217, Fingerprint (SHA-1): E9A33881A51A9C8CB5EA30C23728CAC2F2479C2A [ INFO ] Connecting to the Engine [ INFO ] Waiting for the host to become operational in the engine. This may take several minutes... Build timed out (after 360 minutes). Marking the build as failed. Build was aborted Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson9180790764453283670.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/785/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/785/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 0

Build failed in Jenkins: ovirt_4.0_he-system-tests #603
by jenkins＠jenkins.phx.ovirt.org 23 Dec '16

23 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/603/changes> Changes: [Yaniv Kaul] Fixes and changes to storage tests [Sandro Bonazzola] ovirt-hosted-engine-ha: added 4.1 branch [Sandro Bonazzola] ovirt-release: move to 4.1 branch [Sandro Bonazzola] cockpit-ovirt: exclude fc23 from 4.1 [Gil Shinar] Fix bugs in sdk yamls ------------------------------------------ [...truncated 1118 lines...] + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/sys umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/sys: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/sys + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/sys.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/sys. + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/shm. + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/dev/pts. + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/cache/yum. + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests>: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests>: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests>: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests.'> ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests.> + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/run/libvirt. + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago: not mounted + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/var/lib/lago. + return 1 + failed=true + for mount in '"${mounts[@]}"' + safe_umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems + local mount=/var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems + local attempt + (( attempt=0 )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems: mountpoint not found + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems: mountpoint not found + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems + (( attempt++ )) + (( attempt < 3 )) + [[ attempt > 0 ]] + sleep 1s + sudo umount --lazy /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems umount: /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems: mountpoint not found + findmnt --kernel --first /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems + (( attempt++ )) + (( attempt < 3 )) + echo 'ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems.' ERROR: Failed to umount /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783/root/proc/filesystems. + return 1 + failed=true + for mock_root in '/var/lib/mock/*' + this_chroot_failed=false + mounts=($(cut -d\ -f2 /proc/mounts | grep "$mock_root" | sort -r)) ++ cut '-d ' -f2 /proc/mounts ++ grep /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783 ++ sort -r + [[ -n '' ]] + false + sudo rm -rf /var/lib/mock/epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e-40783 + find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 + xargs -0 -tr sudo rm -rf ++ virsh list --all --uuid + true + echo 'Cleanup script failed, propegating failure to job' Cleanup script failed, propegating failure to job + exit 1 POST BUILD TASK : FAILURE END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 1

[JIRA] (OVIRT-972) Fwd: Maintainership request
by Barak Korren (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-972?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-972: ---------------------------------- Assignee: Shlomo Ben David (was: infra) > Fwd: Maintainership request > --------------------------- > > Key: OVIRT-972 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-972 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support > ---------- Forwarded message ---------- > From: Amit Aviram <aaviram(a)redhat.com> > Date: 22 December 2016 at 15:16 > Subject: Maintainership request > To: infra <infra(a)ovirt.org> > Hi > We need to add the following users as maintainers of ovirt-imageio please: > derez > laravot > Thanks, Amit > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
by Greg Sheremeta (oVirt JIRA) 22 Dec '16

22 Dec '16

Greg Sheremeta created OVIRT-973: ------------------------------------ Summary: nightly ovirt-engine build is missing Chrome permutation Key: OVIRT-973 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Greg Sheremeta Assignee: infra mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. >From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] {noformat} 21:13:24 [INFO] Compiling 1 permutation 21:13:24 [INFO] Compiling permutation 0... 21:16:54 [INFO] Compile of permutations succeeded {noformat} That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. mburman reports this started on November 30. I'm not sure what changed. Adding build flags will fix: DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-971) Fwd: changes in gerrit - backport does not include reviewers automatically
by Barak Korren (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-971?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-971: ---------------------------------- Assignee: Shlomo Ben David (was: infra) > Fwd: changes in gerrit - backport does not include reviewers automatically > -------------------------------------------------------------------------- > > Key: OVIRT-971 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-971 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support > ---------- Forwarded message ---------- > From: Yaniv Bronheim <ybronhei(a)redhat.com> > Date: 22 December 2016 at 16:25 > Subject: changes in gerrit - backport does not include reviewers automatically > To: infra <infra(a)ovirt.org> > A backport with same change-id as in master branch used to add the > reviewer of the original patch automatically. and also the reviewed-on > label with link to the original patch. > can we add it back? > -- > Yaniv Bronhaim. > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-972) Fwd: Maintainership request
by Barak Korren (oVirt JIRA) 22 Dec '16

22 Dec '16

Barak Korren created OVIRT-972: ---------------------------------- Summary: Fwd: Maintainership request Key: OVIRT-972 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-972 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support ---------- Forwarded message ---------- From: Amit Aviram <aaviram(a)redhat.com> Date: 22 December 2016 at 15:16 Subject: Maintainership request To: infra <infra(a)ovirt.org> Hi We need to add the following users as maintainers of ovirt-imageio please: derez laravot Thanks, Amit _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-971) Fwd: changes in gerrit - backport does not include reviewers automatically
by Barak Korren (oVirt JIRA) 22 Dec '16

22 Dec '16

Barak Korren created OVIRT-971: ---------------------------------- Summary: Fwd: changes in gerrit - backport does not include reviewers automatically Key: OVIRT-971 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-971 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support ---------- Forwarded message ---------- From: Yaniv Bronheim <ybronhei(a)redhat.com> Date: 22 December 2016 at 16:25 Subject: changes in gerrit - backport does not include reviewers automatically To: infra <infra(a)ovirt.org> A backport with same change-id as in master branch used to add the reviewer of the original patch automatically. and also the reviewed-on label with link to the original patch. can we add it back? -- Yaniv Bronhaim. _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs
by Barak Korren (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-938?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-938: ------------------------------------ Tested to see if behaviour would different when running on an EL7 host (right now its running in an EL7 chroot on a Fedora host) http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/777 Same results. I'm beginning to suspect it something the tests are doing, same hosts run Lago fine for other things. [~ybronhei(a)redhat.com] Thinks it may be this patch: https://gerrit.ovirt.org/#/c/68078/ He sent an email to devel, investigation will continue. > Fix Jenkins slave connection dying on vdsm check_merged jobs > ------------------------------------------------------------ > > Key: OVIRT-938 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-938 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Something in the vdsm build_artifacs job makes the Jenkins slave disconnect when it is running. This in turn makes the cleanup scripts not run on the slave leaving it dirty enough to make the next job on that slave fail. > Example of this can be seen here: > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console > Relevant log lines: > {code} > 21:49:00 Ran 44 tests in 1231.988s > 21:49:00 > 21:49:00 OK > 21:49:00 + return 0 > 21:49:00 sh: [13086: 1 (255)] tcsetattr: Inappropriate ioctl for device > 21:49:00 Took 2464 seconds > 21:49:00 =================================== > 21:49:00 logout > 21:49:01 Slave went offline during the build > 21:49:01 ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) > 21:49:01 Caused by: java.io.EOFException > 21:49:01 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353) > 21:49:01 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822) > 21:49:01 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) > 21:49:01 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301) > 21:49:01 at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) > 21:49:01 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > 21:49:01 > 21:49:01 Build step 'Execute shell' marked build as failure > 21:49:01 Performing Post build task... > 21:49:01 Match found for :.* : True > 21:49:01 Logical operation result is TRUE > 21:49:01 Running script : #!/bin/bash -x > 21:49:01 echo "shell-scripts/mock_cleanup.sh" > ... SNIP ... > 21:49:01 Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[fc24-vm06.phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@30863c81 and has channel null > 21:49:01 Build step 'Post build task' marked build as failure > 21:49:02 ERROR: Step ?Archive the artifacts? failed: no workspace for vdsm_master_check-merged-el7-x86_64 #692 > 21:49:02 ERROR: Failed to evaluate groovy script. > 21:49:02 java.lang.NullPointerException: Cannot invoke method child() on null object > 21:49:02 at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77) > 21:49:02 at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) > 21:49:02 at Script1.run(Script1.groovy:2) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) > 21:49:02 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:166) > 21:49:02 at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:361) > 21:49:02 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) > 21:49:02 at hudson.model.Build$BuildExecution.post2(Build.java:185) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) > 21:49:02 at hudson.model.Run.execute(Run.java:1763) > 21:49:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) > 21:49:02 at hudson.model.ResourceController.execute(ResourceController.java:98) > 21:49:02 at hudson.model.Executor.run(Executor.java:410) > 21:49:02 Build step 'Groovy Postbuild' marked build as failure > 21:49:02 Started calculate disk usage of build > 21:49:02 Finished Calculation of disk usage of build in 0 seconds > 21:49:02 Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-970: ----------------------------------------------- Assignee: Pavel Zhukov (was: infra) This can get started regardless of the projects who wish to join, we need to have the support in templates,triggers,builders first, so when we want to add new projects, the templates will be ready. Most of the work should start at: (on jenkins repo) jobs/confs/yaml/triggers/github.yml jobs/confs/yaml/templates/standard-stage.yml > Add support for GitHub projects in standard CI > ---------------------------------------------- > > Key: OVIRT-970 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: Pavel Zhukov > > Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 > We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. > We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-970: -------------------------------------------- Epic Link: OVIRT-400 > Add support for GitHub projects in standard CI > ---------------------------------------------- > > Key: OVIRT-970 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 > We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. > We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

eyal edri [Administrator] created OVIRT-970: ----------------------------------------------- Summary: Add support for GitHub projects in standard CI Key: OVIRT-970 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-969) Install new gerrit plugin: Gerrit webhooks plugin
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-969?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-969: -------------------------------------------- Epic Link: OVIRT-403 > Install new gerrit plugin: Gerrit webhooks plugin > ------------------------------------------------- > > Key: OVIRT-969 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-969 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > Info at https://github.com/GetBadges/gerrit-webhooks. > cc [~sbendavi(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-969) Install new gerrit plugin: Gerrit webhooks plugin
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

eyal edri [Administrator] created OVIRT-969: ----------------------------------------------- Summary: Install new gerrit plugin: Gerrit webhooks plugin Key: OVIRT-969 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-969 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Info at https://github.com/GetBadges/gerrit-webhooks. cc [~sbendavi(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4369 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 Dec '16

22 Dec '16

------=_Part_122_182305068.1482407495345 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4369/, Build Number: 4369, Build Status: FAILURE ------=_Part_122_182305068.1482407495345--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4365 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 Dec '16

22 Dec '16

------=_Part_106_599148934.1482399766403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4365/, Build Number: 4365, Build Status: FAILURE ------=_Part_106_599148934.1482399766403--

1 2

[JIRA] (OVIRT-296) [jenkins] take offline faulty bad slaves
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-296?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-296: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > [jenkins] take offline faulty bad slaves > ---------------------------------------- > > Key: OVIRT-296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-296 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > Labels: jenkins, monitoring, > > it seems that quite often we hit an issue with a specific slave on phx, due to various reasons (out of space/git/network/etc..). > which leads to multiple jobs trying to run on it and failing. > we need an automated way of finding this. > proposal: > add post groovy build to jobs that will take a slave offline if it's misbehaves using: > manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true) > the trick is to find such a slave and to be able to know if it failed consistently in the past X hours to justify it's disable. > we need some sort of counter or service to track slaves and thier error state and according to it take offline a specific slave. > for example: > if a slave was failing x jobs in Y time and runtime was < Z min , it might indicate such a problem. > (e.g 10 jobs were failing on the same slave in a timeframe of 5 min and job runtime was less than a 1 min.. ) > the post script should email infra(a)ovirt.org that it disabled a slave and we should look into it. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-226: -------------------------------------------- Resolution: Won't Do (was: Won't Fix) Status: Done (was: To Do) Already tracked by QE, see more info on the Bugzilla bug. > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-20) Document oVirt infra SLA
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-20?page=com.atlassian.jira.pl… ] eyal edri [Administrator] reassigned OVIRT-20: ---------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Document oVirt infra SLA > ------------------------- > > Key: OVIRT-20 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-20 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: quaid > Assignee: Evgheni Dereveanchin > Priority: Highest > > We need to document how we make changes: > * What services need notices out to the world? > * What are the timeframes for notices? > \\- 1 hour for critical > \\- 12 to 24 hours for non-critical > * Who needs to be notified for what? > \\- e.g. leave announce out of administrivia > \\- arch, users, and infra are the defaults so far > \\- perhaps create an infra-announce list that just includes the others? > * When do we not make changes? > \\- change freeze around releases > \\- other change freeze reasons > * What is the process to make a change during a freeze? > \\- When is the freeze slushy? > \\- When is the freeze solid and should not be broken because of the potential risk at that moment? (We need something to weigh risk against risk.) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4362 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 Dec '16

22 Dec '16

------=_Part_99_1942029806.1482395139819 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4362/, Build Number: 4362, Build Status: FAILURE ------=_Part_99_1942029806.1482395139819--

1 2

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-935: ----------------------------------------------- Assignee: bkorren (was: infra) > Unable to build fc25 chroots with mock > -------------------------------------- > > Key: OVIRT-935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Nadav Goldin > Assignee: bkorren > > Mock fails when trying to build the chroot for fedora25, on installing '@buildsys-build' group(with dnf) stage. > Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781 > Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file. > Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always install 'libcrypt' first. > Until fixed this will block us from building anything with mock on fc25(hit it when trying to build fc25 RPMs for lago). > Error logs: > {code} > DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated', '--installroot', '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/', '--releasever', '25', 'install', '@buildsys-build', 'git', 'python', 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils', '--setopt=tsflags=nocontexts'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', > .... > DEBUG util.py:421: Yum command has been deprecated, use dnf instead. > DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. > DEBUG util.py:421: Error: libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64 > DEBUG util.py:421: Error: libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64 > DEBUG util.py:421: You could try using --skip-broken to work around the problem > DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest > DEBUG util.py:557: Child return code was: 1 > DEBUG util.py:180: kill orphans > {code} -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-968) Import image-tools in gerrit
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-968?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-968: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > Import image-tools in gerrit > ---------------------------- > > Key: OVIRT-968 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-968 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: eyal edri [Administrator] > > Please import https://github.com/fabiand/image-tools.git > in ovirt gerrit. > Thanks, > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4346 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 Dec '16

22 Dec '16

------=_Part_62_2131878986.1482341264978 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4346/, Build Number: 4346, Build Status: FAILURE ------=_Part_62_2131878986.1482341264978--

1 14

[JIRA] (OVIRT-968) Import image-tools in gerrit
by sbonazzo (oVirt JIRA) 22 Dec '16

22 Dec '16

sbonazzo created OVIRT-968: ------------------------------ Summary: Import image-tools in gerrit Key: OVIRT-968 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-968 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Please import https://github.com/fabiand/image-tools.git in ovirt gerrit. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-938?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-938: ------------------------------------ Got this from the slave log in Jenkis: {code} ERROR: Connection terminated ESC[8mha:AAAAWB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=ESC[0mjava.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Slave JVM has terminated. Exit signal=TERM [12/21/16 15:23:34] [SSH] Connection closed. {code} > Fix Jenkins slave connection dying on vdsm check_merged jobs > ------------------------------------------------------------ > > Key: OVIRT-938 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-938 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Something in the vdsm build_artifacs job makes the Jenkins slave disconnect when it is running. This in turn makes the cleanup scripts not run on the slave leaving it dirty enough to make the next job on that slave fail. > Example of this can be seen here: > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console > Relevant log lines: > {code} > 21:49:00 Ran 44 tests in 1231.988s > 21:49:00 > 21:49:00 OK > 21:49:00 + return 0 > 21:49:00 sh: [13086: 1 (255)] tcsetattr: Inappropriate ioctl for device > 21:49:00 Took 2464 seconds > 21:49:00 =================================== > 21:49:00 logout > 21:49:01 Slave went offline during the build > 21:49:01 ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) > 21:49:01 Caused by: java.io.EOFException > 21:49:01 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353) > 21:49:01 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822) > 21:49:01 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) > 21:49:01 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301) > 21:49:01 at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) > 21:49:01 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > 21:49:01 > 21:49:01 Build step 'Execute shell' marked build as failure > 21:49:01 Performing Post build task... > 21:49:01 Match found for :.* : True > 21:49:01 Logical operation result is TRUE > 21:49:01 Running script : #!/bin/bash -x > 21:49:01 echo "shell-scripts/mock_cleanup.sh" > ... SNIP ... > 21:49:01 Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[fc24-vm06.phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@30863c81 and has channel null > 21:49:01 Build step 'Post build task' marked build as failure > 21:49:02 ERROR: Step ?Archive the artifacts? failed: no workspace for vdsm_master_check-merged-el7-x86_64 #692 > 21:49:02 ERROR: Failed to evaluate groovy script. > 21:49:02 java.lang.NullPointerException: Cannot invoke method child() on null object > 21:49:02 at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77) > 21:49:02 at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) > 21:49:02 at Script1.run(Script1.groovy:2) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) > 21:49:02 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:166) > 21:49:02 at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:361) > 21:49:02 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) > 21:49:02 at hudson.model.Build$BuildExecution.post2(Build.java:185) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) > 21:49:02 at hudson.model.Run.execute(Run.java:1763) > 21:49:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) > 21:49:02 at hudson.model.ResourceController.execute(ResourceController.java:98) > 21:49:02 at hudson.model.Executor.run(Executor.java:410) > 21:49:02 Build step 'Groovy Postbuild' marked build as failure > 21:49:02 Started calculate disk usage of build > 21:49:02 Finished Calculation of disk usage of build in 0 seconds > 21:49:02 Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

Fwd: Fedora 23 End Of Life
by Sandro Bonazzola 21 Dec '16

21 Dec '16

FYI. ---------- Messaggio inoltrato ---------- Da: "Mohan Boddu" <mboddu(a)redhat.com> Data: 21/Dic/2016 04:05 Oggetto: Fedora 23 End Of Life A: <announce(a)lists.fedoraproject.org>, < test-announce(a)lists.fedoraproject.org>, < devel-announce(a)lists.fedoraproject.org> Cc: As of the 20th of December 2016, Fedora 23 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 23. A previous reminder was sent on 28th of November 2016 [0]. Fedora 24 will continue to receive updates until approximately one month after the release of Fedora 26. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [1]. The Fedora Project wiki also contains instructions [2] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0]https://lists.fedoraproject.org/archives/list/devel@lists. fedoraproject.org/thread/HLHKRTIB33EDZXP624GHF2OZLHWAGKSJ/# Q5O44X4BEBOYEKAEVLSXVI44DSNVHBYG [1]https://fedoraproject.org/wiki/Fedora_Release_Life_ Cycle#Maintenance_Schedule [2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4345 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 21 Dec '16

21 Dec '16

------=_Part_60_303540134.1482341048711 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4345/, Build Number: 4345, Build Status: SUCCESS ------=_Part_60_303540134.1482341048711--

1 0

[JIRA] (OVIRT-954) Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable
by Evgheni Dereveanchin (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-954?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-954: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable > ---------------------------------------------------------------- > > Key: OVIRT-954 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-954 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > The lists server is not reachable anymore. Looks like a dns issue: > $ traceroute lists.ovirt.org > lists.ovirt.org: Name or service not known > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-938?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-938: ------------------------------------ Trying to get more info about this, here are the journal lines we get on the slave when the job fails: {code} Dec 21 15:23:34 vm0136.workers-phx.ovirt.org libvirtd[17504]: End of file while reading data: Input/output error Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_END pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_LOGOUT pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1106 audit(1482333814.930:3694): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1113 audit(1482333814.930:3695): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1112 audit(1482333814.952:3696): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1105 audit(1482333814.952:3697): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_LOGIN pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_START pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5 direction=? spid=25269 suid=1012 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=2404 audit(1482333814.953:3698): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5 direction=? spid=25269 suid=1012 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org sshd[5421]: Received disconnect from 66.187.230.92 port 53024:11: Closed due to user request. Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=2404 audit(1482333814.989:3699): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5 direction=? spid=5421 suid=1012 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=2404 audit(1482333814.989:3700): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=session fp=? direction=both spid=5421 suid=1012 rport=53024 laddr=172.19.12.136 lport=22 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5 direction=? spid=5421 suid=1012 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=session fp=? direction=both spid=5421 suid=1012 rport=53024 laddr=172.19.12.136 lport=22 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org sshd[5421]: Disconnected from 66.187.230.92 port 53024 Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1106 audit(1482333814.995:3701): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog acct="jenkins" exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1104 audit(1482333814.995:3702): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="jenkins" exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1106 audit(1482333814.996:3703): pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_END pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog acct="jenkins" exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRED_DISP pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="jenkins" exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_END pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_LOGOUT pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:c1:30:1f:20:35:5f:1a:4a:cc:9f:c9:eb:05:0c:0f:41:06:32:52:d7:d3:e9:fc:0a:aa:ae:f4:ce:98:15:b3:4c direction=? spid=5410 suid=0 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:3d:5f:aa:8f:5f:6d:01:ba:8a:6c:ca:2a:ae:4e:78:f6:19:cd:44:7c:df:6a:4d:58:ef:be:16:c0:41:b9:a8:a4 direction=? spid=5410 suid=0 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5 direction=? spid=5410 suid=0 exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success' Dec 21 15:23:34 vm0136.workers-phx.ovirt.org sshd[5410]: pam_unix(sshd:session): session closed for user jenkins Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd-logind[444]: Removed session 3. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[1]: Stopping User Manager for UID 1012... Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Stopped target Default. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Stopped target Basic System. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Stopped target Timers. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Stopped target Paths. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Stopped target Sockets. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Closed D-Bus User Message Bus Socket. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Reached target Shutdown. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Starting Exit the Session... Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[5414]: Received SIGRTMIN+24 from PID 25273 (kill). Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[1]: Stopped User Manager for UID 1012. Dec 21 15:23:35 vm0136.workers-phx.ovirt.org audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user@1012 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 21 15:23:35 vm0136.workers-phx.ovirt.org systemd[1]: Removed slice User Slice of jenkins. {code} > Fix Jenkins slave connection dying on vdsm check_merged jobs > ------------------------------------------------------------ > > Key: OVIRT-938 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-938 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Something in the vdsm build_artifacs job makes the Jenkins slave disconnect when it is running. This in turn makes the cleanup scripts not run on the slave leaving it dirty enough to make the next job on that slave fail. > Example of this can be seen here: > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console > Relevant log lines: > {code} > 21:49:00 Ran 44 tests in 1231.988s > 21:49:00 > 21:49:00 OK > 21:49:00 + return 0 > 21:49:00 sh: [13086: 1 (255)] tcsetattr: Inappropriate ioctl for device > 21:49:00 Took 2464 seconds > 21:49:00 =================================== > 21:49:00 logout > 21:49:01 Slave went offline during the build > 21:49:01 ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) > 21:49:01 Caused by: java.io.EOFException > 21:49:01 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353) > 21:49:01 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822) > 21:49:01 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) > 21:49:01 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301) > 21:49:01 at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) > 21:49:01 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > 21:49:01 > 21:49:01 Build step 'Execute shell' marked build as failure > 21:49:01 Performing Post build task... > 21:49:01 Match found for :.* : True > 21:49:01 Logical operation result is TRUE > 21:49:01 Running script : #!/bin/bash -x > 21:49:01 echo "shell-scripts/mock_cleanup.sh" > ... SNIP ... > 21:49:01 Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[fc24-vm06.phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@30863c81 and has channel null > 21:49:01 Build step 'Post build task' marked build as failure > 21:49:02 ERROR: Step ?Archive the artifacts? failed: no workspace for vdsm_master_check-merged-el7-x86_64 #692 > 21:49:02 ERROR: Failed to evaluate groovy script. > 21:49:02 java.lang.NullPointerException: Cannot invoke method child() on null object > 21:49:02 at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77) > 21:49:02 at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32) > 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) > 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) > 21:49:02 at Script1.run(Script1.groovy:2) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) > 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) > 21:49:02 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:166) > 21:49:02 at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:361) > 21:49:02 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) > 21:49:02 at hudson.model.Build$BuildExecution.post2(Build.java:185) > 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) > 21:49:02 at hudson.model.Run.execute(Run.java:1763) > 21:49:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) > 21:49:02 at hudson.model.ResourceController.execute(ResourceController.java:98) > 21:49:02 at hudson.model.Executor.run(Executor.java:410) > 21:49:02 Build step 'Groovy Postbuild' marked build as failure > 21:49:02 Started calculate disk usage of build > 21:49:02 Finished Calculation of disk usage of build in 0 seconds > 21:49:02 Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4340 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 21 Dec '16

21 Dec '16

------=_Part_46_1404524996.1482329430633 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4340/, Build Number: 4340, Build Status: FAILURE ------=_Part_46_1404524996.1482329430633--

1 3

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-967: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ Maybe assign the ticket to yourself if you're handling it.... > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ n/m saw it, so you're doing everything from YAML, so this is the kind of implementation I would call specific, a generic implementation would specify soemthing to put in the automation dir so nobody needs to know YAML... > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ which patch? I'm not seeing any patch linked here... > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-967: ------------------------------------------------- Not sure I understand, the current patch is as generic as it gets without any relation to getbadgets or gamification, If its merged nothing will happen on CI (already verified) because the URL for the webhook is empty by default. Only if you provide a URL as param from a project then its activated, for e.g for jenkins project: https://gerrit.ovirt.org/#/c/68903/1/jobs/confs/projects/jenkins/jenkins_st… The alternative is to create a new template for it and change multiple projects to use it if we want, which I don't see a reason for, if by default the plugin is not active. > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-955) Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
by Marc Dequènes (Duck) (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-955?page=com.atlassian.jira.p… ] Marc Dequènes (Duck) commented on OVIRT-955: -------------------------------------------- yes, a few days ago. the progress was on the migration ticket. > Re: http://lists.ovirt.org/pipermail/announce/ is not reachable > --------------------------------------------------------------- > > Key: OVIRT-955 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-955 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Tested it, I've access forbidden there: > http://lists.phx.ovirt.org/pipermail/announce/ > archives should be publicly accessible. > On Mon, Dec 12, 2016 at 2:21 PM, Evgheni Dereveanchin <ederevea(a)redhat.com> > wrote: > > I totally agree with Barak on this. The hostname > > must work as there's a bunch of links indexed > > by search engine which lead to it. > > In general the PHX one should not be used > > by end users. I've re-added the CNAME and edited > > the virtualhost on apache so it should be available > > again once existing DNS caches expire. > > > > Regards, > > Evgheni Dereveanchin > > > > ----- Original Message ----- > > From: "Barak Korren" <bkorren(a)redhat.com> > > To: "Eyal Edri" <eedri(a)redhat.com> > > Cc: "infra" <infra(a)ovirt.org>, "Sandro Bonazzola" <sbonazzo(a)redhat.com>, > > "Evgheni Dereveanchin" <ederevea(a)redhat.com>, "duck" <duck(a)redhat.com>, > > infra-owner(a)ovirt.org > > Sent: Monday, 12 December, 2016 2:05:57 PM > > Subject: Re: http://lists.ovirt.org/pipermail/announce/ is not reachable > > > > It can be reached now at lists.phx.ovirt.org (but we we need a CNAME > > from the old name) > > > > On 12 December 2016 at 15:03, Eyal Edri <eedri(a)redhat.com> wrote: > > > I'm not sure who gets emails sent to infra-owner list. best to send it > > to > > > infra or infra support. > > > > > > Adding Evgheni and Duck who are working on migration of the mm server. > > > > > > On Dec 12, 2016 2:58 PM, "Sandro Bonazzola" <sbonazzo(a)redhat.com> wrote: > > >> > > >> The lists server is not reachable anymore. Looks like a dns issue: > > >> > > >> $ traceroute lists.ovirt.org > > >> lists.ovirt.org: Name or service not known > > >> > > >> > > >> -- > > >> Sandro Bonazzola > > >> Better technology. Faster innovation. Powered by community > > collaboration. > > >> See how it works at redhat.com > > > > > > > > > _______________________________________________ > > > Infra mailing list > > > Infra(a)ovirt.org > > > http://lists.phx.ovirt.org/mailman/listinfo/infra > > > > > > > > > > > -- > > Barak Korren > > bkorren(a)redhat.com > > RHCE, RHCi, RHV-DevOps Team > > https://ifireball.wordpress.com/ > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ The big question is if we want to have it generic, which will require extensions to the CI standard, and some thinking and perhaps some non-trivial Jenkins tricks, or, we just want to quickly support GetBadges. > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4338 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 21 Dec '16

21 Dec '16

------=_Part_38_542710353.1482325391232 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4338/, Build Number: 4338, Build Status: FAILURE ------=_Part_38_542710353.1482325391232--

1 1

Gerrit hooks doesn't mark open patches in other branches as -verified
by Tal Nisan 21 Dec '16

21 Dec '16

Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862 https://gerrit.ovirt.org/#/c/68861 Those are 4.1 and 4.0 patches that are open on master, I'd expect to see them get -verified from the hooks which they didn't: - Update Tracker::#1406042::OK, status: POST - Check Bug-Url::OK - Check Product::#1406042::OK, product: ovirt-engine - Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor target milestone: ovirt-4.0.7 - Set POST::#1406042::IGNORE, bug is already in 'POST' status - Check Backport::IGNORE, The patch backported to all newer branches.(open in 'master' branch/es) found not relevant branch/es: 'ovirt-engine-4.0' (not exist in the newer branches list) This was the flow before and it made my life easier as I didn't have to actively search for cherry-picks in all other branches to see if it can be merged

3 7

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-967: ------------------------------------------------- Forgot to add the link to the game: https://ovirt-ovirt-engine.getbadges.io/activity > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-967: ------------------------------------------------- Of course it doesn't only have to serve GetBadgets, we can use it in the future to capture events from Jenkins from other systems, one example will be a reporting system that can aggregate results into a cental datawarehouse which we can then create reports from. > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-967: ------------------------------------------------- any project which will want to use it need to pass the URL as parameter > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-967: ------------------------------------------------- Integration with GetBadges Gamification which is working nice until now with the GitHub integration, this will allow oVirt users/developers to get badges / points on having successful builds ( or lose on failing builds ). We already got positive feedback from developers on it, and adding another integration will increase visibility of the game [1] and hopefully make oVirt more fun to use/fix bugs/make ci happy. Fedora has something similar which works well [1] [1] https://badges.fedoraproject.org/ > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ Why do we want this? > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-952) CI-1 unrelated to patch
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-952?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-952: ------------------------------------ I can't analyse this now, b/c I don't have the logs any more. We did not wait for two weeks there was a Jira malfunction that made ticket-opening mails to reach the right place for the last two weeks up until a few hours ago. If this was any real infra issue we probably have already resolved it back then. If it is a repeating issue we probably have other tickets about it. There is no information on this ticket that I can investigate any further. (An no, just the Jenkins exception is NEVER enough, the real reason is typically a few scores of lines above it) This seems reminiscent on OVIRT-938, I wouldn't mark this as duplicate though b/c we're not talking about vdsm check_merged here. > CI-1 unrelated to patch > ----------------------- > > Key: OVIRT-952 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-952 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > An ovirt-engine patch has got -1 for a failing job: > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/146… > Triggered by Gerrit: https://gerrit.ovirt.org/67308 > [EnvInject] - Loading node environment variables. > FATAL: java.io.IOException: Unexpected termination of the channel > hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > at hudson.remoting.Request.abort(Request.java:303) > at hudson.remoting.Channel.terminate(Channel.java:847) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) > at ......remote call to vm0129.workers-phx.ovirt.org(Native Method) > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) > at hudson.remoting.Request.call(Request.java:172) > at hudson.remoting.Channel.call(Channel.java:780) > at hudson.FilePath.act(FilePath.java:1074) > at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44) > at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81) > at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39) > at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:572) > at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:492) > at hudson.model.Run.execute(Run.java:1738) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) > at hudson.model.ResourceController.execute(ResourceController.java:98) > at hudson.model.Executor.run(Executor.java:410) > Caused by: java.io.IOException: Unexpected termination of the channel > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) > Caused by: java.io.EOFException > at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353) > at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822) > at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) > at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301) > at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) > at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > Performing Post build task... > Match found for :.* : True -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

eyal edri [Administrator] created OVIRT-967: ----------------------------------------------- Summary: add support for notification plugin in standard CI Key: OVIRT-967 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-967: -------------------------------------------- Epic Link: OVIRT-400 > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-965) Force check-patch to run on latest-tested
by Daniel Belenky (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-965?page=com.atlassian.jira.p… ] Daniel Belenky reassigned OVIRT-965: ------------------------------------ Assignee: Daniel Belenky (was: infra) > Force check-patch to run on latest-tested > ----------------------------------------- > > Key: OVIRT-965 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-965 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > https://gerrit.ovirt.org/#/c/68896/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-966) Optimize check-patch.sh
by Daniel Belenky (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-966?page=com.atlassian.jira.p… ] Daniel Belenky reassigned OVIRT-966: ------------------------------------ Assignee: Daniel Belenky (was: infra) > Optimize check-patch.sh > ----------------------- > > Key: OVIRT-966 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-966 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > check-patch.sh is fully automatic, and can recognize new suites automatically. > The only demand is to follow the standard naming (must end with *-<version>) > https://gerrit.ovirt.org/#/c/68682/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-966) Optimize check-patch.sh
by Daniel Belenky (oVirt JIRA) 21 Dec '16

21 Dec '16

Daniel Belenky created OVIRT-966: ------------------------------------ Summary: Optimize check-patch.sh Key: OVIRT-966 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-966 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra check-patch.sh is fully automatic, and can recognize new suites automatically. The only demand is to follow the standard naming (must end with *-<version>) https://gerrit.ovirt.org/#/c/68682/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0