October 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-757: ------------------------------------------------- Few questions: 1. Which tests will run there? same as check-patch/check-merged? 2. How will the travis configuration be managed/configured 3. Why use another CI system when we can run it on jenkins.ovirt.org? is there any limitation to existing jenkins server that Travis doesn't have? can you elaborate? > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

2 1

oVirt infra daily report - unstable production jobs - 123
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_404_2004505292.1477868406756 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/123//artifact/exported-a… Cheers, Jenkins ------=_Part_404_2004505292.1477868406756 Content-Type: application/octet-stream; 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 - 30/10/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/deploy-to-ovirt_experimental_master/">deploy-to-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/ovirt-engine-api-model_4.0_build-artifacts-fc2…">ovirt-engine-api-model_4.0_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-engine_master_build-artifacts-el7-x86_64/">ovirt-engine_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-engine_master_coverity-analysis/">ovirt-engine_master_coverity-analysis</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_master_upgrade-from-3.6_el7_merge…">ovirt-engine_master_upgrade-from-3.6_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-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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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_3.6_image-ng-system-tests/">ovirt_3.6_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.0_he-system-tests/">ovirt_4.0_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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-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/repoman_master_check-merged-el7-x86_64/">repoman_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/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/scan_security_and_license_ovirt-engine_master/">scan_security_and_license_ovirt-engine_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/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</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> ------=_Part_404_2004505292.1477868406756--

1 0

[JIRA] (OVIRT-797) [gerrit hooks] update tracker failed to update bugs
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-797?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-797: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] update tracker failed to update bugs > --------------------------------------------------- > > Key: OVIRT-797 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-797 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > Priority: High > > bool(x) function isn't converts 'True' | 'False' strings into bool (True | False) values, > it only returns True if the passed value is True, False otherwise. > I've replaced it with ast.literal_eval() function that converts and returns the required bool values. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-797) [gerrit hooks] update tracker failed to update bugs
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

Shlomo Ben David created OVIRT-797: -------------------------------------- Summary: [gerrit hooks] update tracker failed to update bugs Key: OVIRT-797 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-797 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomo Ben David Assignee: infra Priority: High bool(x) function isn't converts 'True' | 'False' strings into bool (True | False) values, it only returns True if the passed value is True, False otherwise. I've replaced it with ast.literal_eval() function that converts and returns the required bool values. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-797) [gerrit hooks] update tracker failed to update bugs
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-797?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-797: ----------------------------------- Epic Link: OVIRT-403 > [gerrit hooks] update tracker failed to update bugs > --------------------------------------------------- > > Key: OVIRT-797 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-797 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomo Ben David > Assignee: infra > Priority: High > > bool(x) function isn't converts 'True' | 'False' strings into bool (True | False) values, > it only returns True if the passed value is True, False otherwise. > I've replaced it with ast.literal_eval() function that converts and returns the required bool values. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-796) [gerrit hooks] recreate set_post hook
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-796?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-796: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] recreate set_post hook > ------------------------------------- > > Key: OVIRT-796 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-796 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > The new hook will follow the bellow guidelines: > * It updates only u/s bugs (oVirt classification) > * It updates the bug status in bugzilla only from NEW to POST -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-796) [gerrit hooks] recreate set_post hook
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

Shlomo Ben David created OVIRT-796: -------------------------------------- Summary: [gerrit hooks] recreate set_post hook Key: OVIRT-796 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-796 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra The new hook will follow the bellow guidelines: * It updates only u/s bugs (oVirt classification) * It updates the bug status in bugzilla only from NEW to POST -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-796) [gerrit hooks] recreate set_post hook
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-796?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-796: ----------------------------------- Epic Link: OVIRT-403 > [gerrit hooks] recreate set_post hook > ------------------------------------- > > Key: OVIRT-796 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-796 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > > The new hook will follow the bellow guidelines: > * It updates only u/s bugs (oVirt classification) > * It updates the bug status in bugzilla only from NEW to POST -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-758) Vdsm docker testing images
by Barak Korren (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-758: ------------------------------------ Building and publishing Docker images should be quite simple to do from std-ci. There is no technical reason why this couldn`t be done directly in VDSM's check-patch.sh or build-artifacts.sh. But maybe mock will require some tweaking. But perhaps the docker files shouldn't be in the vdsm repo for the sake of not building them unnecessarily, this can also be avoided with a simple condition in the script file though. > Vdsm docker testing images > -------------------------- > > Key: OVIRT-758 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images. > See https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:d… > Currently I maintain the images in docker hub: > - https://hub.docker.com/r/nirs/vdsm-centos/ > - https://hub.docker.com/r/nirs/vdsm-fedora/ > I configured automatic build, so each time I push a change to this branch: > https://github.com/nirs/vdsm/tree/dockerfile > Docker go and rebuilds the images. > We want to move the images to docker hub ovirt account: > https://hub.docker.com/u/ovirt/ > And configure vdsm github project so docker will rebuild > the images when we push a changes to the dockerfile branch, > or another solution to allow easy update of the images by > merging a new dockerfile. > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-754) Guest name 'TestNode-node' is already in use.
by eyal edri [Administrator] (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-754?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-754: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) since the patch with the cleanup was merged, setting as resolved. Please reopen if the problem wasn't fixed. > Guest name 'TestNode-node' is already in use. > --------------------------------------------- > > Key: OVIRT-754 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-754 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… > ====================================================================== > ERROR: test suite for <class 'testSanity.TestNode'> > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/nose/suite.py", line 208, in run > self.setUp() > File "/usr/lib/python2.7/site-packages/nose/suite.py", line 291, in setUp > self.setupContext(ancestor) > File "/usr/lib/python2.7/site-packages/nose/suite.py", line 314, in > setupContext > try_run(context, names) > File "/usr/lib/python2.7/site-packages/nose/util.py", line 469, in try_run > return func() > File > "/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng/tests/testVirt.py", > line 150, in setUpClass > 77) > File > "/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng/tests/testVirt.py", > line 88, in _start_vm > dom = VM.create(name, img, ssh_port=ssh_port, memory_gb=memory_gb) > File > "/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng/tests/virt.py", > line 217, in create > dom = sh.virt_install(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/sh.py", line 1021, in __call__ > return RunningCommand(cmd, call_args, stdin, stdout, stderr) > File "/usr/lib/python2.7/site-packages/sh.py", line 486, in __init__ > self.wait() > File "/usr/lib/python2.7/site-packages/sh.py", line 500, in wait > self.handle_command_exit_code(exit_code) > File "/usr/lib/python2.7/site-packages/sh.py", line 516, in > handle_command_exit_code > raise exc(self.ran, self.process.stdout, self.process.stderr) > ErrorReturnCode_1: > RAN: '/bin/virt-install --import --print-xml --network=user,model=virtio > --noautoconsole --memory=2048 --rng=/dev/random --memballoon=virtio > --cpu=host --vcpus=4 --graphics=vnc --watchdog=default,action=poweroff > --serial=pty > --disk=path=/var/tmp/TestNode-node.qcow2,bus=virtio,format=qcow2,driver_type=qcow2,discard=unmap,cache=unsafe > --check=all=off --channel=unix,target_type=virtio,name=local.test.0 > --name=TestNode-node' > STDOUT: > STDERR: > ERROR Guest name 'TestNode-node' is already in use. > Seems to be a run in a not clean environment. Not sure about what caused > this. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0