- Infra - oVirt List Archives

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #847
by jenkins＠jenkins.phx.ovirt.org 25 Oct '17

25 Oct '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/847/displa…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 6c110aba1bc5436f81eec5d57fbe551eb2b3059e (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6c110aba1bc5436f81eec5d57fbe551eb2b3059e Commit message: "Added production CI jobs for Kubevirt" > git rev-list 6c110aba1bc5436f81eec5d57fbe551eb2b3059e # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins280454292498122609.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1478, in _commonLoadRepoXML self._revertOldRepoXML() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1323, in _revertOldRepoXML os.rename(old_data['old_local'], old_data['local']) OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 70 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Oct '17

25 Oct '17

------=_Part_157_347346443.1508815488935 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/70/ Build Number: 70 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #70 [Yaniv Kaul] Split host add verification check. [Gil Shinar] Added upstream_sources.yaml path to gerrit trigger conf ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-master-host1 is in non operational state -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x3115500> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 153, in _host_is_up raise RuntimeError('Host %s is in non operational state' % host.name()) RuntimeError: Host lago-hc-basic-suite-master-host1 is in non operational state --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 164, in add_hosts testlib.assert_true_within(_host_is_up, timeout=15 * 60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 153, in _host_is_up raise RuntimeError('Host %s is in non operational state' % host.name()) 'Host lago-hc-basic-suite-master-host1 is in non operational state\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x3115500>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 153, in _host_is_up\n raise RuntimeError(\'Host %s is in non operational state\' % host.name())\nRuntimeError: Host lago-hc-basic-suite-master-host1 is in non operational state\n--------------------- >> end captured logging << ---------------------' ------=_Part_157_347346443.1508815488935--

1 1

oVirt infra daily report - unstable production jobs - 484
by jenkins＠jenkins.phx.ovirt.org 25 Oct '17

25 Oct '17

------=_Part_173_1303074046.1508886002030 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/484//artifact/exported-a… Cheers, Jenkins ------=_Part_173_1303074046.1508886002030 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 - 24/10/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-system-tests_hc-basic-suite-master/">ovirt-system-tests_hc-basic-suite-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_173_1303074046.1508886002030--

1 0

[JIRA] (OVIRT-1689) Improve error messages in STDCI environment variable handling
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508875170-18269-631 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1689: -------------------------------- Summary: Improve error messages in STDCI environment variable handling (was: Improve error messages ) > Improve error messages in STDCI environment variable handling > ------------------------------------------------------------- > > Key: OVIRT-1689 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > * All references to things like 'xdg-home' need to be replaced with specifications of actual paths, as users are not expected to know what XDG is. > * Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages. > * When variable/key names are given in error messages, they need to be quoted for clarity. > * Edge cases like for example an existing but empty secrets file and a missing 'secrets_data' key need to be handled better, with clear error messages > * Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use 'mock_runner.sh' for the 'jenkins' repo for example. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508875170-18269-631 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1689:</h3> <pre>Summary: Improve error messages in STDCI environment variable handling (was: Improve error messages )</pre> <blockquote><h3>Improve error messages in STDCI environment variable handling</h3> <pre> Key: OVIRT-1689 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Daniel Belenky Assignee: infra</pre> <ul><li><p>All references to things like ‘xdg-home’ need to be replaced with specifications of actual paths, as users are not expected to know what XDG is.</p></li> <li><p>Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages.</p></li> <li><p>When variable/key names are given in error messages, they need to be quoted for clarity.</p></li> <li><p>Edge cases like for example an existing but empty secrets file and a missing ‘secrets_data’ key need to be handled better, with clear error messages</p></li> <li><p>Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use ‘mock_runner.sh’ for the ‘jenkins’ repo for example.</p></li></ul></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1508875170-18269-631--

1 0

[JIRA] (OVIRT-1219) Pupulate staging jenkins
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1219?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1219: ----------------------------------- Assignee: Barak Korren (was: infra) > Pupulate staging jenkins > ------------------------ > > Key: OVIRT-1219 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1219 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Low > Labels: jenkins, staging > > The staging Jenkins instance currently contains only a few jobs that were created manually. These jobs do not resemble production jobs at all, nor is there any activity going on on that instance that simulates production work. > We can populate the staging Jenkins instance with the following steps: > # Setup the Gerrit plugin in the staging Jenkins to also listen to events from the production Gerrit. > # Create a '{{staging-projects}}' directory on the '{{/jobs/confs}}' directory of the '{{jenkins}}' repo. This way the production YAML job templates can be used to create jobs in the staging Jenkins. > # Create a '{{jenkins_master_deploy-configs_merged}}' job for the staging Jenkins that will deploy jobs from the directory mentioned above. The job template should probably be changed so that the name of the dorectory it will take jobs from will come from a global variable defined in the Jenkins server. > # Create some Standard-CI dummy projects in the staging Gerrit. Setup jobs to occasionally submit random patches to these projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[CQ]: 83125,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 24 Oct '17

24 Oct '17

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

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1143: ----------------------------------- Assignee: Barak Korren (was: infra) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: Barak Korren > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[JIRA] (OVIRT-1128) Add Jenkins job for testing
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508868183-10536-389 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1128: -------------------------------- Resolution: Fixed Status: Done (was: To Do) We have full CI flows running in the staging system now > Add Jenkins job for testing > --------------------------- > > Key: OVIRT-1128 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Pavel Zhukov > Assignee: infra > Labels: staging > > it'd be good to have jenkins job to test and regenerate jenkins jobs :) > which uses "good" jjb configuration and available for infra team from > any machine. > Currently local JJB instances and configs are used which is not perfect > because configs can be different as well as jjb versions, not rebased > repos can be used for testing Besides of that it requires copying of > configs between machines and so on. > -- > Pavel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508868183-10536-389 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1128:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <p>We have full CI flows running in the staging system now</p> <blockquote><h3>Add Jenkins job for testing</h3> <pre> Key: OVIRT-1128 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Pavel Zhukov Assignee: infra Labels: staging</pre> <p>it'd be good to have jenkins job to test and regenerate jenkins jobs :) which uses “good” jjb configuration and available for infra team from any machine. Currently local JJB instances and configs are used which is not perfect because configs can be different as well as jjb versions, not rebased repos can be used for testing Besides of that it requires copying of configs between machines and so on. — Pavel</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1508868183-10536-389--

1 0

[JIRA] (OVIRT-1124) Automate oVirt official release process
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1124?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1124: ----------------------------------- Assignee: Barak Korren (was: infra) > Automate oVirt official release process > --------------------------------------- > > Key: OVIRT-1124 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1124 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: Barak Korren > > Current release flow is 100% manual and depends on multiple sources of built RPMs. > We should support one automated flow which will use the standard CI to build and publish official oVirt releases. > Some initial thoughts to consider: > * We'll need to trigger 'build-artifacts' job when a new tag is added to project and build the official release ( in ovirt-engine we do it already with a special if in build-artifacts.sh ) > * The new RPMS should pass OST / Experimental verification and deployed to 'pre' repo after verification. > * We should support only this flow and not external build systems like koji/copr, any project maintainer that still wants to build in other system is welcome, but for oVirt repos we'll do it from the official tag > * Consider using repoman for signing the RPMs when we compose the 'pre' repo > * If a project doesn't have a new tag to build from, we'll use the latest official release of that project. > [~bkorren@redhat.com][~amarchuk][~sbonazolla@redhat.com] thoughts? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508867991-21521-355 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1014: ----------------------------------- Assignee: Daniel Belenky (was: infra) > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: Daniel Belenky > Labels: standard-ci > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508867991-21521-355 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1014:</h3> <pre>Assignee: Daniel Belenky (was: infra)</pre> <blockquote><h3>avoid repetition in automation/*packages</h3> <pre> Key: OVIRT-1014 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: Daniel Belenky Labels: standard-ci</pre> <p>Currently we have many automation/*packages* files, mostly repeating each other. Most of the information there is then repeated in vdsm.spec as well. It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1508867991-21521-355--

1 0