- Infra - oVirt List Archives

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- If he has merge rights on master, then yes. Maybe its a good idea to ask the vdsm maintainers who should have merge rights on master ( i.e belongs in the master maintainers group ) > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > 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.610.2#100023)

1 0

[JIRA] (OVIRT-870) Access to artifactory.ovirt.org is slow
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-870?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-870: ------------------------------------------------- [~gshinar] Did we solved the slowness issue on artifactory? > Access to artifactory.ovirt.org is slow > --------------------------------------- > > Key: OVIRT-870 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-870 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Juan Hernández > Assignee: infra > > Access to artifactory.ovirt.org seems to be very slow now. For example, > in the following build: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_check-patch-fc24… > It is responding with a transfer rate of 0.2 KiB per second: > Downloaded: > http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/apache/maven/plug… > (7 KB at 0.2 KB/sec) > Can this be improved? > -- > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > 3ºD, 28016 Madrid, Spain > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-856) Re: Jenkins permissions required
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-856?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-856: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: Jenkins permissions required > -------------------------------- > > Key: OVIRT-856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-856 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > On Nov 20, 2016 12:43, "Yanir Quinn" <yquinn(a)redhat.com> wrote: > > Hi, > > I require Jenkins permissions on the following instances in order to > > create my own custom builds (run Build with Parameters): > > > > http://jenkins.ovirt.org/job/ovirt-engine_4.0_build- > > artifacts-el7-x86_64-manual/ > > > > http://jenkins.ovirt.org/job/ovirt-engine_master_build- > > artifacts-el7-x86_64_build_from_patch/ > > > > my user name is : yquinn > > > > Thank you > > Yanir Quinn > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-896) Re: Jenkins issues
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-896?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-896: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) Please try to help [~fdeutsch] debug the issue > Re: Jenkins issues > ------------------ > > Key: OVIRT-896 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-896 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > better to send such info to infra-support to document as a ticket. ( adding > infra-support ) > On Thu, Dec 1, 2016 at 12:22 PM, Fabian Deutsch <fdeutsch(a)redhat.com> wrote: > > Hey, > > > > so - I have an issue > > this job: > > is often picking a wrong commit! > > http://jenkins.ovirt.org/user/fabiand/my-views/view/ovirt- > > node-ng/job/ovirt-node-ng_master_build-artifacts-el7- > > x86_64/219/consoleFull > > > > It says it resetted to master, but master is actually a different commit. > > I observed this a few times in the recent days. > > > > Does somebody have an idea why this could be happening? > > > > 00:00:02.156 Checking out Revision > > c1970c6f7a6404e8ab030147eec81233905345cf (origin/master) > > > > on my local host: > > $ git rev-parse FETCH_HEAD^{commit} # timeout=10 > > 9123c1fd3ce15b02f2e69efdc367ae1477193aef > > > > c1970c6f7a6404e8ab030147eec81233905345cf -- does actually no exist (in > > my history) > > > > - fabian > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by Shlomo Ben David (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] Shlomo Ben David commented on OVIRT-900: ---------------------------------------- Hi, Nope, the 'Forge author Identity' is set specifically with the following permissions: 'vdsm-master-maintainers' group for the 'master' branch 'vdsm-stable-maintainers' group for 'stable' branches - The user ybronhei(a)redhat.com is a member of 'vdsm-stable-maintainers' and 'vdsm-arch-dependencies' groups - The user is not a member of 'vdsm-master-maintainers' group. Should I add him to the 'vdsm-master-maintainers' group? Best Regards, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1 On Thu, Dec 1, 2016 at 6:17 PM, eyal edri [Administrator] (oVirt JIRA) < > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > 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.610.2#100023)

1 0

[JIRA] (OVIRT-871) unrelated CI failure
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-871?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-871: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) We had an issue with the artifactory server which was resolved. > unrelated CI failure > -------------------- > > Key: OVIRT-871 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-871 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Change https://gerrit.ovirt.org/#/c/67101/ just failed on > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/80… > which I believe is utterly unrelated to the patch. please resolved the underlying problem. > [ERROR] Failed to execute goal on project restapi-definition: Could not resolve dependencies for project org.ovirt.engine.api:restapi-definition:jar:4.1.0-SNAPSHOT: Failed to collect dependencies at org.ovirt.engine.api:metamodel-runtime:jar:1.1.8: Failed to read artifact descriptor for org.ovirt.engine.api:metamodel-runtime:jar:1.1.8: Could not transfer artifact org.ovirt.engine.api:metamodel-runtime:pom:1.1.8 from/to ovirt-maven-repository (http://artifactory.ovirt.org/artifactory/ovirt-mirror) Failed to transfer file: http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/ovirt/engine/api/…. Return code is: 502 , ReasonPhrase:Proxy Error. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcept… > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :restapi-definition > Makefile:256: recipe for target 'maven' failed > make[1]: *** [maven] Error 1 > make[1]: Leaving directory '/home/jenkins/workspace/ovirt-engine_master_check-patch-fc24-x86_64/ovirt-engine/rpmbuild/BUILD/ovirt-engine-4.1.0' > Makefile:263: recipe for target 'tmp.built' failed > make: *** [tmp.built] Error 2 > error: Bad exit status from /var/tmp/rpm-tmp.2ykGhi (%build) -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-827) el6 proxy issues
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-827?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-827: -------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) https://ovirt-jira.atlassian.net/browse/OVIRT-645 > el6 proxy issues > ---------------- > > Key: OVIRT-827 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-827 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > 3.6 el6 nightly builder is failing downloading rpms, looks like a proxy > issue: > http://jenkins.ovirt.org/job/ovirt-engine_3.6_build-artifacts-el6-x86_64/15… > DEBUG util.py:421: > http://proxy.phx.ovirt.org:5000/centos-updates/6/x86_64/Packages/python-lib…: > [Errno 14] curl#18 - "transfer closed with 5563146 bytes remaining to read" > DEBUG util.py:421: Trying other mirror. > DEBUG util.py:421: > http://proxy.phx.ovirt.org:5000/centos-updates/6/x86_64/Packages/tzdata-201…: > [Errno 14] curl#18 - "transfer closed with 435320 bytes remaining to read" > DEBUG util.py:421: Trying other mirror. > DEBUG util.py:421: Error downloading packages: > DEBUG util.py:421: python-libs-2.6.6-66.el6_8.x86_64: [Errno 256] No > more mirrors to try. > DEBUG util.py:421: tzdata-2016h-1.el6.noarch: [Errno 256] No more > mirrors to try. > -- > 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.610.2#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- [~sbendavi(a)redhat.com] maybe missing 'forge author identity' permission missing to all 'master branch maintaines'? > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > 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.606.0#100023)

2 1

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by Barak Korren (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-902: ------------------------------------ [~ykaul] The packages install is done by mock itself during the setup of the chroot - so could probably be sped up. All the rest: * The pip stuff * The autogen w/o locale * other package installs All come from inside check_patch.sh (from vdsm repo) so do not belong on this ticket. Having said that, yum in the mock env is running through oVirt's proxy - so not really going to the internet (pre-post install script still takt time though which is why the mock setup is long). We could probably find one way or another to make pip go through the proxy too to make it a little faster (Maybe export the "_http_proxy_" env var in to the mock env .to make scripts able to leverage it). Looking deeper into our scripts, this can be found in mock_cleanup.sh: {code} # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* {code} We probably need need remove that before we can gain any speed ups. But we must heed David's warning and make sure we zap the caches frequently enough so we don't fill up the slaves. > Speed up mock_runner.sh setup time by using caches. > --------------------------------------------------- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: mock, mock_runner.sh, standard-ci > > We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 102 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

------=_Part_216_393019192.1480831436516 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/102/ Build Number: 102 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #102 No changes ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_216_393019192.1480831436516--

1 2

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-902: ------------------------------------------------- I think we see the slowness also on experimental flows, same actions which takes a few seconds w/o mock takes 2 min when running with mock runner. So we should probably give priority to checking the caching options. > Speed up mock_runner.sh setup time by using caches. > --------------------------------------------------- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: mock, mock_runner.sh, standard-ci > > We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by Yaniv Kaul (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.p… ] Yaniv Kaul commented on OVIRT-902: ---------------------------------- 1. I'm not sure if it's here or requires a different ticket, but this is SLOW (taken from http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5101/conso… ): *00:01:28.338* INFO: installing package(s): autoconf automake gdb git libguestfs-tools-c libselinux-python3 libvirt-python3 m2crypto make mom openvswitch policycoreutils-python PyYAML python-blivet python-coverage python2-decorator python-devel python-inotify python-ioprocess python-mock python-netaddr python-pthreading python-setuptools python-six python-requests python3-decorator python3-netaddr python3-nose python3-six python3-yaml rpm-build sanlock-python sudo yum yum-utils *00:03:48.999* INFO: None 2:20 to install packages, is VERY slow. 2. Then there are the pip stuff - which probably are also going somewhere off to the 'net: 00:03:52.839 + easy_install pip ... 00:03:53.401 + pip install -U tox==2.1.1 ... 00:03:55.843 Downloading pluggy-0.3.1-py2.py3-none-any.whl 00:03:55.868 Installing collected packages: virtualenv, py, pluggy, tox 00:03:56.223 Successfully installed pluggy-0.3.1 py-1.4.31 tox-2.1.1 virtualenv-15.1.0 So only 4 seconds, but probably not needed at all. 3. Why not set locale? 00:03:56.670 + ./autogen.sh --system --enable-hooks --enable-vhostmd 00:03:56.678 perl: warning: Setting locale failed. 00:03:56.678 perl: warning: Please check that your locale settings: 00:03:56.679 LANGUAGE = (unset), 00:03:56.679 LC_ALL = (unset), 00:03:56.679 LANG = "en_US.UTF-8" 4. The 5 seconds here are probably due to slow storage! 00:04:05.096 client/Makefile.am:23: installing 'build-aux/py-compile' 00:04:10.239 Running ./configure with --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=/usr/lib64 --enable-hooks --enable-vhostmd 5. This is also going out to the Internet? 00:04:14.989 + debuginfo-install -y python ... 00:04:30.879 glibc-debuginfo-common.x86_64 0:2.23.1-11.fc24 6. Again some more deps: 00:05:23.621 tox -e tests 00:05:23.912 tests create: /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/.tox/tests 00:05:29.991 tests installdeps: nose==1.3.7 7. it's not clear if the nose tests are running in parallel. Is that supported by VDSM tests? 8. Not sure what is going on here: 00:09:34.017 + coverage html -d /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/exported-artifacts/htmlcov 00:09:49.213 + popd 00:09:49.213 ~ 00:09:49.213 + shopt -s extglob 00:09:49.213 + git diff-tree --no-commit-id --name-only -r HEAD 00:09:49.213 + egrep --quiet 'vdsm.spec.in|Makefile.am' 00:19:07.994 Took 915 seconds > Speed up mock_runner.sh setup time by using caches. > --------------------------------------------------- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: mock, mock_runner.sh, standard-ci > > We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by Yedidyah Bar David (oVirt JIRA) 04 Dec '16

04 Dec '16

Yedidyah Bar David created OVIRT-903: ---------------------------------------- Summary: master-to-master CI upgrade tests Key: OVIRT-903 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi all, Recently a patch to the engine [1] added a new package, with a certain set of dependencies, which broke upgrade. This is similar to [2] but for a new package. CI wasn't affected, I think because of [3]. To make CI test such flows, we should have a job that: 1. Builds, installs and sets up the version we want to test 2. Pushes a dummy change to the local git repo (to force a new version), build the patched tree, create a yum repo with the build and add it to yum.repos.d. 3. yum update 4. engine-setup Another option is to revert [3], or to duplicate - have both "upgrade current to self" and "upgrade latest snapshot to current". The downside is that it will be checked later than above plan - instead of in the same build, will only be tested in the first build that uses the snapshot after it was updated, and also will be misleading, as the reason why that job failed will not be apparent (which was why [3] was added). Please handle. I can of course try to help. Best, [1] https://gerrit.ovirt.org/66999 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 [3] https://gerrit.ovirt.org/67263 -- Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-901) bad mirror caused check-merged jobs to fail
by Barak Korren (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-901?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-901: ------------------------------------ One approach to setting up a mirror that never fails is to make it "transactional" by actually seyting up a whole new mirror every time you sync it and then create some kind of a meta-data file that point to where it is. That way when a job starts running it just takes the latest meta-data file in it is guaranteed that the thing this file points to will never change while the job is running. This doesn't mean that syncing the mirror will be slow, there are quite a few things we can do to make it fast: * Use hardlinks - before running the mirror sync tool (reposync, repoman, rsync, etc.) copy the older mirror (by creating hardlinks so the copy is fast) to the new location. * Use LVM snapshots - Always sync the mirror to the same place, but after the sync is done, create an LVM snapshot of that place, mount it and put the location it is mounted into as the path in the metadata file. * Use a tool the has this kind of functionality built-in (Katallo/Pulp with content views) > bad mirror caused check-merged jobs to fail > ------------------------------------------- > > Key: OVIRT-901 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-901 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > check-merged jobs fails on bad mirrors: > If we can't defend ourselves from repomd.xml file errors, lets setup a mirror when we control the mirror sync and we can decide on the update times ( maybe even disable jenkins jobs when the update is running to avoid errors ) > http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/103/console > 07:35:30 Can't download or revert repomd.xml for check-epel-el7 > 07:35:30 Some dependencies may not be complete for this repository > 07:35:30 Run as root to get all dependencies or use -t to enable a user temp cache > 07:35:30 Checking Dependencies > 07:35:30 failure: repodata/151a911cc4b434fcd135e243eec4a4f1d8c1943595a92e2bb838cda5f03577ff-primary.sqlite.xz from check-epel-el7: [Errno 256] No more mirrors to try. > 07:35:30 http://mirror.switch.ch/ftp/mirror/epel/7/x86_64/repodata/151a911cc4b434fcd…: [Errno 14] HTTP Error 404 - Not Found -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by Barak Korren (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-902: ------------------------------- Labels: mock mock_runner.sh standard-ci (was: ) > Speed up mock_runner.sh setup time by using caches. > --------------------------------------------------- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: mock, mock_runner.sh, standard-ci > > We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by Barak Korren (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-902: ------------------------------- Epic Link: OVIRT-400 > Speed up mock_runner.sh setup time by using caches. > --------------------------------------------------- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > > We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by Barak Korren (oVirt JIRA) 04 Dec '16

04 Dec '16

Barak Korren created OVIRT-902: ---------------------------------- Summary: Speed up mock_runner.sh setup time by using caches. Key: OVIRT-902 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra Priority: High We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: * root_cache_enable * yum_cache_enable Both these options should be set to true in the mock chroot config file. We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-901) bad mirror caused check-merged jobs to fail
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

eyal edri [Administrator] created OVIRT-901: ----------------------------------------------- Summary: bad mirror caused check-merged jobs to fail Key: OVIRT-901 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-901 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra check-merged jobs fails on bad mirrors: If we can't defend ourselves from repomd.xml file errors, lets setup a mirror when we control the mirror sync and we can decide on the update times ( maybe even disable jenkins jobs when the update is running to avoid errors ) http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/103/console 07:35:30 Can't download or revert repomd.xml for check-epel-el7 07:35:30 Some dependencies may not be complete for this repository 07:35:30 Run as root to get all dependencies or use -t to enable a user temp cache 07:35:30 Checking Dependencies 07:35:30 failure: repodata/151a911cc4b434fcd135e243eec4a4f1d8c1943595a92e2bb838cda5f03577ff-primary.sqlite.xz from check-epel-el7: [Errno 256] No more mirrors to try. 07:35:30 http://mirror.switch.ch/ftp/mirror/epel/7/x86_64/repodata/151a911cc4b434fcd…: [Errno 14] HTTP Error 404 - Not Found -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-901) bad mirror caused check-merged jobs to fail
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-901?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-901: -------------------------------------------- Epic Link: OVIRT-403 > bad mirror caused check-merged jobs to fail > ------------------------------------------- > > Key: OVIRT-901 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-901 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > check-merged jobs fails on bad mirrors: > If we can't defend ourselves from repomd.xml file errors, lets setup a mirror when we control the mirror sync and we can decide on the update times ( maybe even disable jenkins jobs when the update is running to avoid errors ) > http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/103/console > 07:35:30 Can't download or revert repomd.xml for check-epel-el7 > 07:35:30 Some dependencies may not be complete for this repository > 07:35:30 Run as root to get all dependencies or use -t to enable a user temp cache > 07:35:30 Checking Dependencies > 07:35:30 failure: repodata/151a911cc4b434fcd135e243eec4a4f1d8c1943595a92e2bb838cda5f03577ff-primary.sqlite.xz from check-epel-el7: [Errno 256] No more mirrors to try. > 07:35:30 http://mirror.switch.ch/ftp/mirror/epel/7/x86_64/repodata/151a911cc4b434fcd…: [Errno 14] HTTP Error 404 - Not Found -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[oVirt Jenkins] repos_master_check-closure_el7_merged - Build # 101 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

------=_Part_218_1374785850.1480834800312 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/ Build: http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/101/ Build Number: 101 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #101 No changes ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_218_1374785850.1480834800312--

1 0

[oVirt Jenkins] repos_4.0_check-closure_el7_merged - Build # 115 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

------=_Part_214_148367180.1480831341457 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/repos_4.0_check-closure_el7_merged/ Build: http://jenkins.ovirt.org/job/repos_4.0_check-closure_el7_merged/115/ Build Number: 115 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #115 No changes ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_214_148367180.1480831341457--

1 0

oVirt infra daily report - unstable production jobs - 157
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

------=_Part_193_435974707.1480806006860 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/157//artifact/exported-a… Cheers, Jenkins ------=_Part_193_435974707.1480806006860 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 03/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/java-ovirt-engine-sdk4_4.0_build-artifacts-el7…">java-ovirt-engine-sdk4_4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_create-iso-el7-x86_64/">ovirt-live_master_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live </h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.0_build-artifacts-e…">python-ovirt-engine-sdk4_4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.0_build-artifacts-f…">python-ovirt-engine-sdk4_4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_master_build-artifact…">python-ovirt-engine-sdk4_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/">system-backup_jenkins_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_193_435974707.1480806006860--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4197 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 03 Dec '16

03 Dec '16

------=_Part_175_1484766329.1480779260542 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4197/, Build Number: 4197, Build Status: SUCCESS ------=_Part_175_1484766329.1480779260542--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4182 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Dec '16

03 Dec '16

------=_Part_148_1770595446.1480742347679 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4182/, Build Number: 4182, Build Status: FAILURE ------=_Part_148_1770595446.1480742347679--

1 1

oVirt infra daily report - unstable production jobs - 156
by jenkins＠jenkins.phx.ovirt.org 03 Dec '16

03 Dec '16

------=_Part_129_1501801790.1480719605763 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/156//artifact/exported-a… Cheers, Jenkins ------=_Part_129_1501801790.1480719605763 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 02/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/java-ovirt-engine-sdk4_4.0_build-artifacts-el7…">java-ovirt-engine-sdk4_4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.0_build-artifacts-e…">python-ovirt-engine-sdk4_4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.0_build-artifacts-f…">python-ovirt-engine-sdk4_4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_master_build-artifact…">python-ovirt-engine-sdk4_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/">system-backup_jenkins_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_129_1501801790.1480719605763--

1 0

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #342
by jenkins＠jenkins.phx.ovirt.org 02 Dec '16

02 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/342/> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/> [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash -xe /tmp/hudson1346644945664492084.sh + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> + mkdir <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> Copied 6 artifacts from "ovirt-host-deploy_master_build-artifacts-el7-x86_64" build number 23 Copied 6 artifacts from "ovirt-host-deploy_master_build-artifacts-fc24-x86_64" build number 13 Copied 8 artifacts from "otopi_master_build-artifacts-el7-x86_64" build number 31 Copied 8 artifacts from "otopi_master_build-artifacts-fc24-x86_64" build number 19 Copied 5 artifacts from "ovirt-vmconsole_master_build-artifacts-el7-x86_64" build number 2 Copied 6 artifacts from "ovirt-vmconsole_master_build-artifacts-fc24-x86_64" build number 1 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-el7-x86_64" build number 61 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-fc24-x86_64" build number 24 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-el7-x86_64" build number 9 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-fc24-x86_64" build number 5 Copied 4 artifacts from "ovirt-log-collector_master_build-artifacts-el7-x86_64" build number 9 Copied 4 artifacts from "ovirt-log-collector_master_build-artifacts-fc24-x86_64" build number 5 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-el7-x86_64" build number 23 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-fc24-x86_64" build number 13 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_master_create-rpms-el7-x86_64_merged" build number 21 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_master_create-rpms-fc24-x86_64_merged" build number 5 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_master_create-rpms-el7-x86_64_merged" build number 5 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_master_create-rpms-el7-x86_64_merged" build number 4 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_master_create-rpms-fc24-x86_64_merged" build number 3 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-el7-x86_64" build number 31 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-fc24-x86_64" build number 11 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_master_create-rpms-el7-x86_64_merged" build number 15 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_master_create-rpms-fc24-x86_64_merged" build number 10 Copied 4 artifacts from "ovirt-setup-lib_master_build-artifacts-el7-x86_64" build number 11 Copied 4 artifacts from "ovirt-setup-lib_master_build-artifacts-fc24-x86_64" build number 7 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-el7-x86_64" build number 42 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-fc24-x86_64" build number 20 Copied 4 artifacts from "ovirt-engine-sdk_master_build-artifacts-el7-x86_64" build number 99 Copied 5 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc24-x86_64" build number 76 Copied 4 artifacts from "python-ovirt-engine-sdk4_master_build-artifacts-el7-x86_64" build number 2 ERROR: Unable to find a build for artifact copy from: python-ovirt-engine-sdk4_master_build-artifacts-fc24-x86_64

1 2

[JIRA] (OVIRT-899) Create locking on experimental flow
by Barak Korren (oVirt JIRA) 02 Dec '16

02 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-899?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-899: ------------------------------------ As we've talked, the code will probably work better over time if the loop is not infinite, like so: {code} MAX_LOCK_ATTEMPTS=120 LOCK_WAIT_INTERVAL=5 LOCK_PATH=$HOME/experimental_repo.lock wait_for_lock() { trap "rm -f '$LOCK_PATH'" EXIT for ((i = 0; i < $MAX_LOCK_ATTEMPTS; i++)); do (set -o noclobber; > $LOCK_PATH) 2> /dev/null && return sleep $LOCK_WAIT_INTERVAL done echo "Timed out waiting for lock" >&2 exit 1 } {code} > Create locking on experimental flow > ----------------------------------- > > Key: OVIRT-899 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-899 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > In order to make experimental flow atomic, we need to do as follows: > in deploy.sh script and in start_testing_latest.sh we need to add a loop in the beginning of each script that does the following: > *while 1: > do > is_locked=$((echo aaa > my.lock) 2> /dev/null || echo is locked) > if [[ -z $is_locked ]]; then > break > else > sleep 5 > fi > done* > Wrap the whole script with a trap so in the end if each script we will be able to remove my.lock no matter what happened. -- This message was sent by Atlassian JIRA (v1000.610.1#100023)

1 0

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

02 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/746/changes> Changes: [Yaniv Kaul] CHAP and IPv6 for iSCSI [Sandro Bonazzola] ovirt-release: add 4.1 branch [Ryan Barry] projects: add appliance builders for 4.1 [Ryan Barry] projects: add 4.1 builder for imgbased [Ryan Barry] projects: add ovirt-node-ng builders for 4.1 ------------------------------------------ [...truncated 1239 lines...] ## took 2653 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 2509 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure 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/hudson3905340880765715474.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/746/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/746/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/746/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then for log in "${logs[@]}" do echo "Copying ${log} to exported-artifacts" mv $log exported-artifacts/ done fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" # Drop all left over libvirt domains for UUID in $(virsh list --all --uuid); do virsh destroy $UUID || : sleep 2 virsh undefine --remove-all-storage --storage vda --snapshots-metadata $UUID || : done [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson1408240487253297486.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + for log in '"${logs[@]}"' + echo 'Copying ./ovirt-system-tests/logs to exported-artifacts' Copying ./ovirt-system-tests/logs to exported-artifacts + mv ./ovirt-system-tests/logs exported-artifacts/ + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + mock_root=epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> ++ virsh list --all --uuid POST BUILD TASK : SUCCESS 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 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3276 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 02 Dec '16

02 Dec '16

------=_Part_50_359079684.1480632115396 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3276/, Build Number: 3276, Build Status: FAILURE ------=_Part_50_359079684.1480632115396--

1 2

oVirt infra daily report - unstable production jobs - 155
by jenkins＠jenkins.phx.ovirt.org 02 Dec '16

02 Dec '16

------=_Part_52_715635920.1480633210108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/155//artifact/exported-a… Cheers, Jenkins ------=_Part_52_715635920.1480633210108 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 01/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86…">ovirt-appliance_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-…">ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/">system-backup_jenkins_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/">vdsm_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/">vdsm_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_52_715635920.1480633210108--

1 0

Deprecating Defaults for to_all_distros Setting in repoman
by Anton Marchukov 01 Dec '16

01 Dec '16

Hello All. If you use repoman please be aware that it currently has hardcoded list of packages that defaults to being distroless. This is controlled by "to_all_distros" configuration setting, but if you do not set it than the defaults are used. For ovirt experimental we decided that we better have all packages to have distro specified in spec. This also inline with most distro packaging guidelines. But then with current defaults repoman will consider those package to be distroless even when they are not and specifying an empty list in configuration is a silly way to override this. This change provides an incompatibility, but you can still use this feature by specifying to_all_distros package list explicitly in the config. So it is just the change of default values at this point: https://gerrit.ovirt.org/#/c/67662/ If somebody is not ok with defaults change and need time to update configuration please let me know. Also if you are not sure we can go another way and have intermediate repoman version that does not do the change, but issue deprecation warning if defaults are being used, so everybody can test their setups. However I think that it is might not be actually needed in this case as it is a configuration thing. Please feel free to comment on change request. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

2 2

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-900: ---------------------------------- Assignee: Shlomo Ben David (was: infra) > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > 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.606.0#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

Barak Korren created OVIRT-900: ---------------------------------- Summary: Re: Rebase over other author's patch cannot be pushed to gerrit Key: OVIRT-900 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support. On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > Not sure since when it was changed, but I noticed that I can't push patches > if I'm not the author > > Counting objects: 50, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (50/50), done. > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > Total 50 (delta 34), reused 0 (delta 0) > remote: Resolving deltas: 100% (34/34) > remote: Processing changes: refs: 1, done > remote: > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > remote: ERROR: author email address rnachimu(a)redhat.com > remote: ERROR: does not match your user account. > remote: ERROR: > remote: ERROR: The following addresses are currently registered: > remote: ERROR: bronhaim(a)gmail.com > remote: ERROR: ybronhei(a)redhat.com > remote: ERROR: > remote: ERROR: To register an email address, please visit: > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > remote: > remote: > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > ! [remote rejected] HEAD -> refs/for/master (invalid author) > error: failed to push some refs to > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > We must have permissions to do that, this is part of the rebasing part, and > I think its fine to fix patches on behalf of someone else.. but its not the > best practice for reviewing. > anyway, please undo this change, unless its something that related only to > my env.. let me know > > Thanks > > -- > 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.606.0#100023)

1 0

Rebase over other author's patch cannot be pushed to gerrit
by Yaniv Bronheim 01 Dec '16

01 Dec '16

Not sure since when it was changed, but I noticed that I can't push patches if I'm not the author Counting objects: 50, done. Delta compression using up to 4 threads. Compressing objects: 100% (50/50), done. Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. Total 50 (delta 34), reused 0 (delta 0) remote: Resolving deltas: 100% (34/34) remote: Processing changes: refs: 1, done remote: remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 remote: ERROR: author email address rnachimu(a)redhat.com remote: ERROR: does not match your user account. remote: ERROR: remote: ERROR: The following addresses are currently registered: remote: ERROR: bronhaim(a)gmail.com remote: ERROR: ybronhei(a)redhat.com remote: ERROR: remote: ERROR: To register an email address, please visit: remote: ERROR: https://gerrit.ovirt.org/#/settings/contact remote: remote: To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm ! [remote rejected] HEAD -> refs/for/master (invalid author) error: failed to push some refs to 'ssh:// ybronhei@gerrit.ovirt.org:29418/vdsm' We must have permissions to do that, this is part of the rebasing part, and I think its fine to fix patches on behalf of someone else.. but its not the best practice for reviewing. anyway, please undo this change, unless its something that related only to my env.. let me know Thanks -- *Yaniv Bronhaim.*

2 1

[JIRA] (OVIRT-899) Create locking on experimental flow
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-899?page=com.atlassian.jira.p… ] Barak Korren edited comment on OVIRT-899 at 12/1/16 5:48 PM: ------------------------------------------------------------- The script as you wrote it above is more complex then it should be. Try this: {code} while ! (> my.lock) 2> /dev/null; do sleep 5 done {code} was (Author: bkorren(a)redhat.com) The script as you wrote it above is more complex then it should be. Try this: {code} while (> my.lock) 2> /dev/null; do sleep 5 done {code} > Create locking on experimental flow > ----------------------------------- > > Key: OVIRT-899 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-899 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > In order to make experimental flow atomic, we need to do as follows: > in deploy.sh script and in start_testing_latest.sh we need to add a loop in the beginning of each script that does the following: > *while 1: > do > is_locked=$((echo aaa > my.lock) 2> /dev/null || echo is locked) > if [[ -z $is_locked ]]; then > break > else > sleep 5 > fi > done* > Wrap the whole script with a trap so in the end if each script we will be able to remove my.lock no matter what happened. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-899) Create locking on experimental flow
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-899?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-899: ------------------------------------ The script as you wrote it above is more complex then it should be. Try this: {code} while (> my.lock) 2> /dev/null; do sleep 5 done {code} > Create locking on experimental flow > ----------------------------------- > > Key: OVIRT-899 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-899 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > In order to make experimental flow atomic, we need to do as follows: > in deploy.sh script and in start_testing_latest.sh we need to add a loop in the beginning of each script that does the following: > *while 1: > do > is_locked=$((echo aaa > my.lock) 2> /dev/null || echo is locked) > if [[ -z $is_locked ]]; then > break > else > sleep 5 > fi > done* > Wrap the whole script with a trap so in the end if each script we will be able to remove my.lock no matter what happened. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-899) Create locking on experimental flow
by Gil Shinar (oVirt JIRA) 01 Dec '16

01 Dec '16

Gil Shinar created OVIRT-899: -------------------------------- Summary: Create locking on experimental flow Key: OVIRT-899 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-899 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra In order to make experimental flow atomic, we need to do as follows: in deploy.sh script and in start_testing_latest.sh we need to add a loop in the beginning of each script that does the following: *while 1: do is_locked=$((echo aaa > my.lock) 2> /dev/null || echo is locked) if [[ -z $is_locked ]]; then break else sleep 5 fi done* Wrap the whole script with a trap so in the end if each script we will be able to remove my.lock no matter what happened. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3266 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 01 Dec '16

01 Dec '16

------=_Part_26_1699353469.1480601985289 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3266/, Build Number: 3266, Build Status: FAILURE ------=_Part_26_1699353469.1480601985289--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4123 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 01 Dec '16

01 Dec '16

------=_Part_24_697741448.1480599438863 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4123/, Build Number: 4123, Build Status: SUCCESS ------=_Part_24_697741448.1480599438863--

1 0

[JIRA] (OVIRT-898) Send committers in test experimental job's email
by Gil Shinar (oVirt JIRA) 01 Dec '16

01 Dec '16

Gil Shinar created OVIRT-898: -------------------------------- Summary: Send committers in test experimental job's email Key: OVIRT-898 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-898 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra I can get the job that triggered deploy experimental and test experimental and get commiters from that job. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-897) ovirt-guest-agent job not building rpms
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-897?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-897: ----------------------------------------------- Assignee: vfeenstr (was: infra) Vincent, can you update the buid-artifacts.sh job to build rpms? > ovirt-guest-agent job not building rpms > --------------------------------------- > > Key: OVIRT-897 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-897 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: vfeenstr > > Hi, please have a look at > http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-el7-x… > ovirt-guest-agent job not building rpms > 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.606.0#100023)

1 0

[JIRA] (OVIRT-897) ovirt-guest-agent job not building rpms
by sbonazzo (oVirt JIRA) 01 Dec '16

01 Dec '16

sbonazzo created OVIRT-897: ------------------------------ Summary: ovirt-guest-agent job not building rpms Key: OVIRT-897 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-897 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, please have a look at http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-el7-x… ovirt-guest-agent job not building rpms 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.606.0#100023)

1 0

[JIRA] (OVIRT-896) Re: Jenkins issues
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-896: ----------------------------------------------- Summary: Re: Jenkins issues Key: OVIRT-896 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-896 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra better to send such info to infra-support to document as a ticket. ( adding infra-support ) On Thu, Dec 1, 2016 at 12:22 PM, Fabian Deutsch <fdeutsch(a)redhat.com> wrote: > Hey, > > so - I have an issue > this job: > is often picking a wrong commit! > http://jenkins.ovirt.org/user/fabiand/my-views/view/ovirt- > node-ng/job/ovirt-node-ng_master_build-artifacts-el7- > x86_64/219/consoleFull > > It says it resetted to master, but master is actually a different commit. > I observed this a few times in the recent days. > > Does somebody have an idea why this could be happening? > > 00:00:02.156 Checking out Revision > c1970c6f7a6404e8ab030147eec81233905345cf (origin/master) > > on my local host: > $ git rev-parse FETCH_HEAD^{commit} # timeout=10 > 9123c1fd3ce15b02f2e69efdc367ae1477193aef > > c1970c6f7a6404e8ab030147eec81233905345cf -- does actually no exist (in > my history) > > - fabian > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

Jenkins issues
by Fabian Deutsch 01 Dec '16

01 Dec '16

Hey, so - I have an issue this job: is often picking a wrong commit! http://jenkins.ovirt.org/user/fabiand/my-views/view/ovirt-node-ng/job/ovirt… It says it resetted to master, but master is actually a different commit. I observed this a few times in the recent days. Does somebody have an idea why this could be happening? 00:00:02.156 Checking out Revision c1970c6f7a6404e8ab030147eec81233905345cf (origin/master) on my local host: $ git rev-parse FETCH_HEAD^{commit} # timeout=10 9123c1fd3ce15b02f2e69efdc367ae1477193aef c1970c6f7a6404e8ab030147eec81233905345cf -- does actually no exist (in my history) - fabian

2 1

[JIRA] (OVIRT-862) Please give Denis Chalygin the usual developer permissions
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-862?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-862: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Please give Denis Chalygin the usual developer permissions > ---------------------------------------------------------- > > Key: OVIRT-862 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-862 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Sivak > Assignee: infra > > We need the usual permissions for Gerrit and Jenkins. His email is > dchaplyg. > -- > Martin Sivak > SLA / oVirt -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-864) Shipment delivery problem #00000870089
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-864?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-864: -------------------------------------------- > Shipment delivery problem #00000870089 > -------------------------------------- > > Key: OVIRT-864 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-864 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx 2Day A.M. > Assignee: infra > > Dear Customer, > Courier was unable to deliver the parcel to you. > Please, open email attachment to print shipment label. > Regards, > Andy Mccormick, > Support Manager. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-866) 54606 infra-support
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-866?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-866: -------------------------------------------- > 54606 infra-support > ------------------- > > Key: OVIRT-866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-866 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: m.kos(a)lycos.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-863) Delivery Notification, ID 1285359132561
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-863?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-863: -------------------------------------------- > Delivery Notification, ID 1285359132561 > --------------------------------------- > > Key: OVIRT-863 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-863 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx Standard Overnight > Assignee: infra > > Hello, > We could not deliver your parcel. You can review complete details of your order in the find attached. > Letizia Nenninger - Area Manager FedEx , CA > Sincerely. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-868) Delivery Notification, ID 837693
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-868?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-868: -------------------------------------------- > Delivery Notification, ID 837693 > -------------------------------- > > Key: OVIRT-868 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-868 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx Standard Overnight > Assignee: infra > > Hello, > We could not deliver your parcel. Please, open email attachment to print shipment label. > Valencia Lindbeck - Area Manager FedEx , CA > Thank you for choosing FedEx. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!
by Evgheni Dereveanchin (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-867: -------------------------------------------- [~sbonazzo(a)redhat.com] is this issue still happening? If yes - can we specify several mirrors for this job as we do for mock configs? > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > 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.606.0#100023)

1 0