- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 244
by jenkins＠jenkins.phx.ovirt.org 27 Feb '17

27 Feb '17

------=_Part_45_1249140496.1488236409151 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/244//artifact/exported-a… Cheers, Jenkins ------=_Part_45_1249140496.1488236409151 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 - 27/02/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-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_4.1_hc-system-tests/">ovirt_4.1_hc-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_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-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_hc-system-tests/">ovirt_master_hc-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_image-ng-system-tests/">ovirt_master_image-ng-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/repos_4.1_check-closure_el7_merged/">repos_4.1_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_4.1_check-closure_fc24_merged/">repos_4.1_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/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/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> ------=_Part_45_1249140496.1488236409151--

1 0

[JIRA] (OVIRT-1202) Need write access to http://resources.ovirt.org/repos/docs/
by eyal edri [Administrator] (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1202?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1202: -------------------------------------------------- resources is a yum repository without external access, its a production system that is being used by all the CI system and holds official releases, its not a documentation placeholder. Currently the oVirt documentation is scattered around GitHub pages ( like ovirt-sdk ) and on ovirt.org Infra team maintains read the doc page to hold all the infra docs [1], you might consider doing the same for your project. if its presentation/videos, then oVirt has its own youtube channel to hold such things. If any of the above doesn't fit the need, then we need to think on an alternate solution, maybe to increase size on GitHub. [~duck][~bproffit(a)redhat.com] - What sort of documentation solution is provided as part of the community cage? is there an option to extend the GitHub space limitation? [1] infra-docs.readthedocs.org > Need write access to http://resources.ovirt.org/repos/docs/ > ----------------------------------------------------------- > > Key: OVIRT-1202 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1202 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marcin Mirecki > Assignee: infra > > Can you please grant me write access on: http://resources.ovirt.org/repos/docs/ > There is a need to host some docs (like presentations) on ovirt site. Ovirt site itself is not a good place for this due to github space limitations. The idea is to host the actual docs here, and link them on ovirt-site. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-682) Improve CI logging
by Barak Korren (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-682: ------------------------------------ One more thing we can do if we implement extended reporting to Gerrit as I suggested above, is let the CI system issue warnings, like for example if the job used external repos instead of mirrors. > Improve CI logging > ------------------ > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > 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.784.2#100032)

1 0

[JIRA] (OVIRT-1202) Need write access to http://resources.ovirt.org/repos/docs/
by Marcin Mirecki (oVirt JIRA) 27 Feb '17

27 Feb '17

Marcin Mirecki created OVIRT-1202: ------------------------------------- Summary: Need write access to http://resources.ovirt.org/repos/docs/ Key: OVIRT-1202 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1202 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Marcin Mirecki Assignee: infra Can you please grant me write access on: http://resources.ovirt.org/repos/docs/ There is a need to host some docs (like presentations) on ovirt site. Ovirt site itself is not a good place for this due to github space limitations. The idea is to host the actual docs here, and link them on ovirt-site. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OST-5) export and import vm
by eyal edri [Administrator] (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OST-5?page=com.atlassian.jira.plugi… ] eyal edri [Administrator] commented on OST-5: --------------------------------------------- duplicate, tracked in Lago GitHub issues. > export and import vm > -------------------- > > Key: OST-5 > URL: https://ovirt-jira.atlassian.net/browse/OST-5 > Project: oVirt system tests > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: infra > > check in the history of ost for the disabled test -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OST-5) export and import vm
by eyal edri [Administrator] (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OST-5?page=com.atlassian.jira.plugi… ] eyal edri [Administrator] updated OST-5: ---------------------------------------- Status: Done (was: To Do) Resolution: Done > export and import vm > -------------------- > > Key: OST-5 > URL: https://ovirt-jira.atlassian.net/browse/OST-5 > Project: oVirt system tests > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: infra > > check in the history of ost for the disabled test -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1073) Drop nightly publishers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1073: -------------------------------------------------- We won't drop the nightly publishers. Instead we'll just stop publishing RPMs from it and it will only be used to sync tested RPMs each night to the snapshot repos, that way we'll have static nightly updated oVirt repos. The code to support it for master is already merged and part of the master publisher. We need to remove all the YAML code from the publisher job gradually until all is left is the code that sync the test repo. fyi [~sbonazolla(a)redhat.com] > Drop nightly publishers in oVirt CI > ----------------------------------- > > Key: OVIRT-1073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > We saw how destructive using the current publishers can be during 4.1 cycle, > Problems we encountered: > 1. It hides missing RPMs from experimental flows > 2. It hides projects that needs to branch or using previous version released > 3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt. > We should aim to drop it for 4.2 and use only experimental deployment. > However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1073) Drop nightly publishers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1073: --------------------------------------------- Status: In Progress (was: Blocked) > Drop nightly publishers in oVirt CI > ----------------------------------- > > Key: OVIRT-1073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > We saw how destructive using the current publishers can be during 4.1 cycle, > Problems we encountered: > 1. It hides missing RPMs from experimental flows > 2. It hides projects that needs to branch or using previous version released > 3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt. > We should aim to drop it for 4.2 and use only experimental deployment. > However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1199) Re: Please add me to the CI white list
by eyal edri [Administrator] (oVirt JIRA) 27 Feb '17

27 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1199?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1199: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: Please add me to the CI white list > -------------------------------------- > > Key: OVIRT-1199 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1199 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > adding infra support to open a ticket. > On Tue, Feb 21, 2017 at 5:58 PM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Hi, please put me to the CI white list on gerrit.ovirt.org so that > > Jenkins runs for my patches. > > > > Thanks, > > Milan > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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.784.2#100032)

1 0

Ovirt Jenkins Account
by Phillip Bailey 27 Feb '17

27 Feb '17

Hi, I need a Jenkins account so that I can retrigger CI builds when necessary. I'm not sure whether an account has been created for me previously. I was going to attempt resetting my password to see if an account exists, but I couldn't find a "reset password" link anywhere. Could you please tell me if I have an account and what the process is for having one created if I don't? Thank you! -Phillip Bailey

2 1