- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #185 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

------=_Part_241_1562252617.1484056640786 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/185/, Build Number: 185, Build Status: FAILURE ------=_Part_241_1562252617.1484056640786--

1 1

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

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- {quote} could work for me. But I would like to be able to specify the version of package, in order to be able to generate spec file Requires: and BuildRequires: directives. {quote} The thing with this is that the '{{*.packages}}' file need to be translated to a single '{{yum install foo bar baz...}}' line. So there is not much versioning logic I can do. You can use exact versions though. I suppose we could implement more complex logic, but that will be equivalent to running '{{yum-builddep}' from inside the automation script (Which means, the results will not be cached, and the installation will be done every single time the job runs). We might be able to do more complex stuff when we get around to OVIRT-873. > 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 > Reporter: danken > Assignee: infra > > 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 (v1000.670.2#100024)

1 0

CI not running on ovirt-engine-dashboard-1.1 branch
by Greg Sheremeta 10 Jan '17

10 Jan '17

Hi, Even after [3] was merged, no CI is running on [1] and [2]. I tried "Re-run hooks: all" but no luck. Any ideas? Something else I need to do? Greg [1] https://gerrit.ovirt.org/#/c/69731/ [2] https://gerrit.ovirt.org/#/c/69735/ [3] https://gerrit.ovirt.org/#/c/69737/ -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com

3 3

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by danken (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] danken commented on OVIRT-1014: ------------------------------- We are using symlinks when possible. #include "./check-patch.packages" could work for me. But I would like to be able to specify the version of package, in order to be able to generate spec file Requires: and BuildRequires: directives. > 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 > Reporter: danken > Assignee: infra > > 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 (v1000.670.2#100024)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4653 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

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

1 3

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #180 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

------=_Part_217_710524236.1484043988492 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/180/, Build Number: 180, Build Status: FAILURE ------=_Part_217_710524236.1484043988492--

1 4

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

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1014 at 1/10/17 3:15 PM: -------------------------------------------------------------- This had been asked for before. If the files are exact replicas symlinks can be used. WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms... WRT having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure. Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file. was (Author: bkorren(a)redhat.com) This had been asked for before. If the files are exact replicas symlinks can be used. WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms... WTR having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure. Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file. > 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 > Reporter: danken > Assignee: infra > > 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 (v1000.670.2#100024)

1 0

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

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- This had been asked for before. If the files are exact replicas symlinks can be used. WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms... WTR having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure. Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file. > 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 > Reporter: danken > Assignee: infra > > 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 (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by danken (oVirt JIRA) 10 Jan '17

10 Jan '17

danken created OVIRT-1014: ----------------------------- Summary: 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 Reporter: danken Assignee: infra 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 (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-754) Guest name 'TestNode-node' is already in use.
by Evgheni Dereveanchin (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-754?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-754: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > 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: Evgheni Dereveanchin > Fix For: OVIRT-INFRA-OCT-2016 > > > 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.670.2#100024)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4651 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4647 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

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

1 3

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-914: ------------------------------- Labels: mock_runner.sh standard-ci (was: ) > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Labels: standard-ci (was: ) > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1013: ------------------------------------- Since this may be a developer-visible change, a message about this was sent to devel: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Description: The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: 1. The platforms a certain project needs to be built and tested on. 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. was: The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: 1. The platforms a certain project needs to be built and tested on. 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

Barak Korren created OVIRT-1013: ----------------------------------- Summary: Automate standard-CI job creation Key: OVIRT-1013 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: 1. The platforms a certain project needs to be built and tested on. 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Epic Link: OVIRT-400 > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-894) Add support of secrets and credentials in Standard-CI
by Barak Korren (oVirt JIRA) 10 Jan '17

10 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-894?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-894: ------------------------------- Summary: Add support of secrets and credentials in Standard-CI (was: Add support of sercers and credentials in Standard-CI) > Add support of secrets and credentials in Standard-CI > ----------------------------------------------------- > > Key: OVIRT-894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-894 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Some task we'd like to carry out in Standard-CI require credentials. Examples for such tasks include: > # Publishing artifacts to repositories (E.g containers to Dokcerhub, puppet code to Puppetmaster) > # Launching remote processes (Check code with remote services) > While Jenkins supports storing and managing secret data, we did not enable a way to use this capability from Standard-CI so far. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

Re: ** PROBLEM Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is WARNING **
by Nadav Goldin 10 Jan '17

10 Jan '17

Looks good now, thanks! Nadav. On Tue, Jan 10, 2017 at 1:38 AM, Neil Bright <ncbright(a)gatech.edu> wrote: > Hi Nadav, > > I was fixing some things earlier this afternoon (around noon US/Eastern). Are you still having reachability issues? > >> On Jan 9, 2017, at 5:06 PM, Nadav Goldin <ngoldin(a)redhat.com> wrote: >> >> Hi, >> Seems like the ovirt mirror went out of sync again, can you have a look? >> >> Thanks, >> >> Nadav. >> >> >> >> ---------- Forwarded message ---------- >> From: icinga <icinga(a)monitoring.ovirt.org> >> Date: Mon, Jan 9, 2017 at 11:51 PM >> Subject: ** PROBLEM Service Alert: >> ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site >> last sync is WARNING ** >> To: ngoldin(a)redhat.com >> >> >> ***** Icinga ***** >> >> Notification Type: PROBLEM >> >> Service: www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync >> Host: ovirt-mirrorchecker >> Address: 66.187.230.105 >> State: WARNING >> >> Date/Time: Mon Jan 9 21:51:19 UTC 2017 >> >> Additional Info: >> >> WARNING - 237938 seconds since last sync, which are 66.0939 hours. > > +======================================================================+ > Neil Bright (ncbright(a)gatech.edu) (404) 385-6954 > http://www.pace.gatech.edu > 258 Fourth Street, Rich Bldg, Rm 321 / Atlanta, GA 30332-0700 > >

1 0

Build failed in Jenkins: ovirt_3.6_he-system-tests #803
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/803/changes> Changes: [Yaniv Kaul] Allow discard for storage ------------------------------------------ [...truncated 653 lines...] Finish: shell @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@ Fri Jan 6 03:00:01 UTC 2017 automation/he_basic_suite_3.6.sh chroot finished @@ took 410 seconds @@ rc = 1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ========== Scrubbing chroot 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="./mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.scrub" \ --scrub=chroot 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 Start: scrub ['chroot'] INFO: scrubbing chroot for mocker-epel-7-x86_64.el7 Finish: scrub ['chroot'] Finish: run Scrub chroot took 6 seconds ============================ ########################################################## ## Fri Jan 6 03:00:07 UTC 2017 Finished env: el7:epel-7-x86_64 ## took 416 seconds ## rc = 1 ########################################################## find: 'logs': No such file or directory No log files found, check command output ##!######################################################## Collecting mock logs './mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.clean_rpmdb' -> 'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.clean_rpmdb' './mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh' -> 'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh' './mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.init' -> 'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.init' ########################################################## 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/hudson5037284079566254380.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/803/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/803/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/ws/ovirt-system-test…> <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/803/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 -x echo "shell-scripts/mock_cleanup.sh" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC shopt -s nullglob WORKSPACE="${WORKSPACE:-$PWD}" UMOUNT_RETRIES="${UMOUNT_RETRIES:-3}" UMOUNT_RETRY_DELAY="${UMOUNT_RETRY_DELAY:-1s}" safe_umount() { local mount="${1:?}" local attempt for ((attempt=0 ; attempt < $UMOUNT_RETRIES ; attempt++)); do # If this is not the 1st time through the loop, Sleep a while to let # the problem "solve itself" [[ attempt > 0 ]] && sleep "$UMOUNT_RETRY_DELAY" # Try to umount sudo umount --lazy "$mount" && return 0 # See if the mount is already not there despite failing findmnt --kernel --first "$mount" > /dev/null && return 0 done echo "ERROR: Failed to umount $mount." return 1 } # 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" # 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 safe_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=($(cut -d\ -f2 /proc/mounts | grep "$mock_root" | sort -r)) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do safe_umount "$mount" && continue # If we got here, we failed $UMOUNT_RETRIES attempts so we should make # noise failed=true this_chroot_failed=true done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done # remove mock caches that are older then 2 days: find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 | \ xargs -0 -tr sudo rm -rf # We make no effort to leave around caches that may still be in use because # packages installed in them may go out of date, so may as well recreate them # 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 if $failed; then echo "Cleanup script failed, propegating failure to job" exit 1 fi [ovirt_3.6_he-system-tests] $ /bin/bash -x /tmp/hudson5918502768537555975.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + UMOUNT_RETRIES=3 + UMOUNT_RETRY_DELAY=1s + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + 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-e30b297ddc7e818ebfbed823dcce8eb8 + [[ -n epel-7-x86_64-e30b297ddc7e818ebfbed823dcce8eb8 ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-e30b297ddc7e818ebfbed823dcce8eb8 + : + [[ -n '' ]] + find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 + xargs -0 -tr sudo rm -rf ++ virsh list --all --uuid + false 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 4

oVirt infra daily report - unstable production jobs - 195
by jenkins＠jenkins.phx.ovirt.org 10 Jan '17

10 Jan '17

------=_Part_206_639461436.1484002804607 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/195//artifact/exported-a… Cheers, Jenkins ------=_Part_206_639461436.1484002804607 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 - 09/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/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-system-tests_master_check-patch-fc24-x86…">ovirt-system-tests_master_check-patch-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_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.1_system-tests/">ovirt_4.1_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.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_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> ------=_Part_206_639461436.1484002804607--

1 0

Fwd: ** PROBLEM Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is WARNING **
by Nadav Goldin 09 Jan '17

09 Jan '17

Hi, Seems like the ovirt mirror went out of sync again, can you have a look? Thanks, Nadav. ---------- Forwarded message ---------- From: icinga <icinga(a)monitoring.ovirt.org> Date: Mon, Jan 9, 2017 at 11:51 PM Subject: ** PROBLEM Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is WARNING ** To: ngoldin(a)redhat.com ***** Icinga ***** Notification Type: PROBLEM Service: www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync Host: ovirt-mirrorchecker Address: 66.187.230.105 State: WARNING Date/Time: Mon Jan 9 21:51:19 UTC 2017 Additional Info: WARNING - 237938 seconds since last sync, which are 66.0939 hours.

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4643 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Jan '17

09 Jan '17

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

1 3

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #174 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Jan '17

09 Jan '17

------=_Part_188_202513061.1483983491038 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/174/, Build Number: 174, Build Status: FAILURE ------=_Part_188_202513061.1483983491038--

1 3

New failure in OST - master branch: add secondary storage domains fails
by Nadav Goldin 09 Jan '17

09 Jan '17

Hi, There is a new failure on on master in experimental flow, the failing test is 'add_secondary_storage_domain', the engine.log has few exceptions: 2017-01-09 10:07:24,943-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-6-thread-2) [e9e4e3b] Command 'PollVDSCommand(HostName = lago-basic-suite-master-host1, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='f6ad90f7-1b37-49f0-a958-7151efa0039c'})' execution failed: VDSGenericException: VDSNetworkException: Timeout during rpc call 2017-01-09 10:07:24,943-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-6-thread-2) [e9e4e3b] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Timeout during rpc call at org.ovirt.engine.core.vdsbroker.vdsbroker.FutureVDSCommand.get(FutureVDSCommand.java:73) [vdsbroker.jar:] ... 2017-01-09 10:10:23,323-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler10) [7cad9211] Command 'GetAllVmStatsVDSCommand(HostName = lago-basic-suite-master-host1, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='f6ad90f7-1b37-49f0-a958-7151efa0039c'})' execution failed: VDSGenericException: VDSNetworkException: Heartbeat exceeded 2017-01-09 10:10:23,323-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler10) [7cad9211] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Heartbeat exceeded at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:188) [vdsbroker.jar:] ... 2017-01-09 10:10:43,704-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Illegal unquoted character ((CTRL-CHAR, code 10)): has to be escaped using backslash to be included in name at [Source: [B@6a84a0d0; line: 1, column: 889]: org.codehaus.jackson.JsonParseException: Illegal unquoted character ((CTRL-CHAR, code 10)): has to be escaped using backslash to be included in name at [Source: [B@6a84a0d0; line: 1, column: 889] at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433) [jackson-core-asl-1.9.13.jar:1.9.13] at org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521) [jackson-core-asl-1.9.13.jar:1.9.13] at org.codehaus.jackson.impl.JsonParserMinimalBase._throwUnquotedSpace(JsonParserMinimalBase.java:482) [jackson-core-asl-1.9.13.jar:1.9.13] at org.codehaus.jackson.impl.ReaderBasedParser._parseFieldName2(ReaderBasedParser.java:1042) [jackson-core-asl-1.9.13.jar:1.9.13] at org.codehaus.jackson.impl.ReaderBasedParser._parseFieldName(ReaderBasedParser.java:1008) [jackson-core-asl-1.9.13.jar:1.9.13] .... <JsonRpcRequest id: "7711f770-dbef-44be-9f9e-2d8a2bfae937", method: Host.getAllVmStats, params: {}> 2017-01-09 10:11:33,336-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler7) [7cad9211] Command 'GetAllVmStatsVDSCommand(HostName = lago-basic-suite-master-host1, VdsIdVDSCommandParameters Base:{runAsync='true', hostId='f6ad90f7-1b37-49f0-a958-7151efa0039c'})' execution failed: VDSGenericException: VDSNetworkException: Unrecognized message received 2017-01-09 10:11:33,336-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler7) [7cad9211] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNe tworkException: Unrecognized message received at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:188) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand.executeVdsBrokerCommand(GetAllVmStatsVDSCommand.java:23) [vdsbroker.jar:] VDSM logs on host1: 2017-01-09 10:11:27,120 ERROR (jsonrpc/4) [storage.StorageDomainCache] domain 80985016-bdd8-4778-abd9-becc8fedcab4 not found (sdc:157) Traceback (most recent call last): File "/usr/share/vdsm/storage/sdc.py", line 155, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 185, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'80985016-bdd8-4778-abd9-becc8fedcab4',) 2017-01-09 10:11:27,452 ERROR (jsonrpc/4) [storage.StorageDomainCache] looking for unfetched domain 80985016-bdd8-4778-abd9-becc8fedcab4 (sdc:151) 2017-01-09 10:11:27,453 ERROR (jsonrpc/4) [storage.StorageDomainCache] looking for domain 80985016-bdd8-4778-abd9-becc8fedcab4 (sdc:168) 2017-01-09 10:11:27,552 WARN (jsonrpc/4) [storage.LVM] lvm vgs failed: 5 [] [' WARNING: Not using lvmetad because config setting use_lvmetad=0.', ' WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).' , ' Volume group "80985016-bdd8-4778-abd9-becc8fedcab4" not found', ' Cannot process volume group 80985016-bdd8-4778-abd9-becc8fedcab4'] (lvm:377) 2017-01-09 10:11:27,559 ERROR (jsonrpc/4) [storage.StorageDomainCache] domain 80985016-bdd8-4778-abd9-becc8fedcab4 not found (sdc:157) Traceback (most recent call last): File "/usr/share/vdsm/storage/sdc.py", line 155, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 185, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'80985016-bdd8-4778-abd9-becc8fedcab4',) 2017-01-09 10:11:27,560 ERROR (jsonrpc/4) [storage.TaskManager.Task] (Task='e2381f1f-eee5-4922-a56d-f6ca40d76eec') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1159, in attachStorageDomain pool.attachSD(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 924, in attachSD dom = sdCache.produce(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 112, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 155, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 185, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'80985016-bdd8-4778-abd9-becc8fedcab4',) .... 2017-01-09 10:19:31,467 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='700015ba-4aed-4eaf-961b-5a4373b2d4d7') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2212, in getAllTasksInfo raise se.SpmStatusError() SpmStatusError: Not SPM: () 2017-01-09 10:19:31,471 INFO (jsonrpc/6) [storage.TaskManager.Task] (Task='700015ba-4aed-4eaf-961b-5a4373b2d4d7') aborting: Task is aborted: 'Not SPM' - code 654 (task:1175) 2017-01-09 10:19:31,471 ERROR (jsonrpc/6) [storage.Dispatcher] {'status': {'message': 'Not SPM: ()', 'code': 654}} (dispatcher:77) 2017-01-09 10:19:31,472 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getAllTasksInfo failed (error 654) in 0.01 seconds (__init__:515) 2017-01-09 10:19:31,479 INFO (jsonrpc/7) [dispatcher] Run and protect: getAllTasksStatuses(spUUID=None, options=None) (logUtils:49) 2017-01-09 10:19:31,479 ERROR (jsonrpc/7) [storage.TaskManager.Task] (Task='2841da07-b3b4-4573-ae38-b1500f793221') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2172, in getAllTasksStatuses raise se.SpmStatusError() SpmStatusError: Not SPM: () 2017-01-09 10:19:31,480 INFO (jsonrpc/7) [storage.TaskManager.Task] (Task='2841da07-b3b4-4573-ae38-b1500f793221') aborting: Task is aborted: 'Not SPM' - code 654 (task:1175) Full engine logs can be found here: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4643/artif… VDSM host1 logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4643/artif… Rest of the logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4643/artif… Could someone take a look? Thanks, Nadav.

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #172 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Jan '17

09 Jan '17

------=_Part_184_297438184.1483980082426 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/172/, Build Number: 172, Build Status: FAILURE ------=_Part_184_297438184.1483980082426--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #169 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Jan '17

09 Jan '17

------=_Part_178_1890642216.1483971936570 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/169/, Build Number: 169, Build Status: FAILURE ------=_Part_178_1890642216.1483971936570--

1 1

[JIRA] (OVIRT-1012) ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0
by Ondra Machacek (oVirt JIRA) 09 Jan '17

09 Jan '17

Ondra Machacek created OVIRT-1012: ------------------------------------- Summary: ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0 Key: OVIRT-1012 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1012 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Ondra Machacek Assignee: infra Hello, The ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0. This isn't correct, it specified branches the project should be build only for el7, fc24 and fc25. Thank you. CC [~jhernand(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

jsonrpc build failures
by Piotr Kliczewski 09 Jan '17

09 Jan '17

I pushed a patch and I can see that all the jobs failed for it: http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_check-patch-el7-x86_6… : FAILURE http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_check-patch-fc24-x86_… : FAILURE http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.1_check-patch-fc24-x86_64/… : FAILURE http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.1_check-patch-el7-x86_64/3/ : FAILURE Can someone please take a look? Thanks, Piotr

1 0

The feature everyone was asking for is finally here...
by Eyal Edri 09 Jan '17

09 Jan '17

FYI, After many requests from multiple developers and testers, the oVirt CI added a new simple job that lets you run the full fledged end-to-end oVirt system tests with a click of a button. You can read all the details and how-to in the new oVirt blog [1]. We wanted to allow running oVirt system tests on EVERY open patch from ANY oVirt project, without relaying on complex building code inside the job. Luckily we just added the 'build-on-demand' so together with it you can build any rpms you'd like and use them to run the manual job. So the 2 steps you'll need to do are: 1. Write 'ci please build' inside a comment on an open oVirt patch ( make sure the feature is enabled for that project first, its already available for ovirt-engine,vdsm,dashboard and vdsm-jsonrpc-java) 2. Run the manual OST job for the version you'd like to test with the URLs you got from #1 You'll get and email once the job is done and you can browse the results and check for logs from engine and the hosts. Please feel free to ask questions on infra(a)ovirt.org as usual. [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 <+972%209-769-2018> irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 3

[JIRA] (OVIRT-1010) Split the experimental pipeline job into stages
by Barak Korren (oVirt JIRA) 09 Jan '17

09 Jan '17

Barak Korren created OVIRT-1010: ----------------------------------- Summary: Split the experimental pipeline job into stages Key: OVIRT-1010 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1010 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Since the experimental flow is based on a pipeline job, we can make debugging it easier by splitting it into stages. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1010) Split the experimental pipeline job into stages
by Barak Korren (oVirt JIRA) 09 Jan '17

09 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1010?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1010: -------------------------------- Epic Link: OVIRT-400 > Split the experimental pipeline job into stages > ----------------------------------------------- > > Key: OVIRT-1010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1010 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Since the experimental flow is based on a pipeline job, we can make debugging it easier by splitting it into stages. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

When trigged manually the check-merged job
by Yaniv Bronheim 09 Jan '17

09 Jan '17

When trigged manually the check-merged job for specific patch we don't see the link in the patch History - see in https://gerrit.ovirt.org/#/c/69802/3 it used to be different .. can we get the link back? Thanks. -- *Yaniv Bronhaim.*

3 2

[JIRA] (OVIRT-853) check out blue ocean jenkins project
by Barak Korren (oVirt JIRA) 09 Jan '17

09 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-853?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-853: ------------------------------------ I have it running in a test container... It required Jenkins 2.7 and up. It run side-by-side with the old Jenkins UI. Its quite good at showing results of pipelines. Some terms important for the analysis below: * *Pipeline stage:* Created with the '{{stage}}' block - collects build steps together and gives then a title. * *Pipeline build step:* Created with commands like '{{sh}}' and {{scm}}. Does actual work like running scripts. The older pipeline stage view (The table we see in the status screen of pipeline jobs) can already show pipeline stages and let you see the logs of separate build steps separately, but its not very good when the pipeline does things in parallel - it just shows the steps one after another. Blue Ocean knows how to show things that happened in parallel separately. Its important to note that both plugins assume that pipeline stages never happen in parallel. This means that debugging complex stuff that happens in parallel can be difficult, since it can be hard to tell separate build steps apart (Most of them are simply called 'Shell script') and we can't give then names by using stages. Both Blue Ocean and the old pipeline stage view do not show the names of the nodes things are running on, this can make some things harder to debug. When pipeline jobs run other jobs - both plugins are not good at showing that, they do not provide clear indication about what is going on or provide links to the invoked jobs. Blue ocean knows how to show the running time of a given piepline, but not of stages inside that pipeline. The pipeline view can show both, so its better for debugging slowness... Blue ocean also cannot show runtime trends. Blue Ocean is not good at showing results of freestyle (old) jobs: * The logs of all build steps are shown together - like in the console view * There is no results screen, so we can't use something like groovy to create better output display. * There is a big and fancy artifacts tab, but it only lets you download artifacts, not view them. Also we need to check how it behaves when we have many artifacts nested inside directories. *Conclusions:* # Blue Ocean requires Jenkins 2 # We should slowly move to pipeline jobs everywhere if we want to get any improved logging. # We should keep pipelines simple - not do complex stuff in parallel, instead split pipelines into serial stages and only do 1-3 steps on parallel within the stage boundaries. # Blue Ocean cannot completely replace the Jenkins UI. # I recommend we install Blue Ocean once we upgrade to Jenkins 2, so we can start gaining real world experience with it. # Over time I expect we will link to Blue Ocean from Gerrit instead of to the old UI. > check out blue ocean jenkins project > ------------------------------------ > > Key: OVIRT-853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-853 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > https://jenkins.io/projects/blueocean/ -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

oVirt infra daily report - unstable production jobs - 194
by jenkins＠jenkins.phx.ovirt.org 09 Jan '17

09 Jan '17

------=_Part_174_926679668.1483916402346 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/194//artifact/exported-a… Cheers, Jenkins ------=_Part_174_926679668.1483916402346 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 - 08/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/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_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.1_system-tests/">ovirt_4.1_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.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_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> ------=_Part_174_926679668.1483916402346--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #151 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Jan '17

08 Jan '17

------=_Part_168_1561606545.1483884140733 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/151/, Build Number: 151, Build Status: FAILURE ------=_Part_168_1561606545.1483884140733--

1 1

Future of the oVirt website
by Marc Dequènes (Duck) 08 Jan '17

08 Jan '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Mf2CRNBB5HrIBekLkGCVl7fFA28A9J5x4 Content-Type: multipart/mixed; boundary="KLQQcoDbkQBSA3JhvJxcIEH58dqc2asks"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Cc: Brian Proffitt <bproffit(a)redhat.com>, Garrett LeSage <garrett(a)redhat.com>, Michael Scherer <misc(a)redhat.com> Message-ID: <70270534-4d06-ef32-0a72-b457c96678fe(a)redhat.com> Subject: Future of the oVirt website --KLQQcoDbkQBSA3JhvJxcIEH58dqc2asks Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, So I just discovered this thread: http://lists.ovirt.org/pipermail/devel/2017-January/029097.html First, it would be nice if the infra team was involved directly, because not everyone is also an oVirt developer (and on this list). Also there are already plans to improve the site system and build and this side-initiative feels like an unexpected and rude disruption of energy already invested. It seems people forget how things were in the past, which leads to going back and forth between a new solution and the previous one. People wish for an easy way to contribute, and this is a legitimate goal. After some time an easy solution make things complicated because it is such a mess and there is no review, so no quality checks, and people wish to have workflows. Then they find it to cumbersome and wish to go back to a marvelous past. And so on again and again. This said, this does not mean the current solution is perfect and we should not think about a better one, but we should recall why we abandoned a wiki to switch to the current solution, so we don't fall into the same traps. What I can say on the topic is that migrating is painful, so we should be cautious. OSAS is not here to force a solution upon you, but the infra team (and the OSAS folks too), have a limited workforce to dedicate to this project, so let's make something realistic. Also we just finish another pass of cleanup of the current site, with migration bugs from the previous Mediawiki solution, so keep in mind it would probably take _years_ to really get something clean. Who's gonna do this?= I also wanted to say I totally disagree on someone's remark (somewhere in the thread) about doc not being as important as code. A lot of content is obsolete or mistaken in the current site already, and this means giving a very bad image of the project, raising the number of silly questions people come to bother you with on ML or IRC, so I think doc should really be taken seriously. As a user it is often I have to dig in the code to find undocumented features, or why a documented one does not work as said, and that's fu^Wutterly boring. So this was to gather all related parties. \_o< --KLQQcoDbkQBSA3JhvJxcIEH58dqc2asks-- --Mf2CRNBB5HrIBekLkGCVl7fFA28A9J5x4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlhvJ5cACgkQVen596wc RD8Ecw//WfXl6FgFg+7R8u84dAhiDiciE/ybTPZDPWldnClTE/+L0toNSiNNBXNd 13HQGnpXpxeCH0JqdzYw0GbJB9DqRhfZBEgw55/BtPG9kPL14bTZrLlZNhvQa8p7 A+i+zAq9I6TbHeR1bY/lNf1cBZYGFRacxihlF6W62lq0jZthV2q3bRX4Fy18yWUD CmwKVKchaGrx4J0SOQ2NO4lh7enwaKpGOTzTsIlIjA+jSSKZAJt2jbKzel+bOfY/ SFDxfp2L539A4pXPDOJ4oRI4fMOZ+aVYpfGT2p+QmwMzaEu1KR4ZF0rXNDNr9SaI M//R3174Rr42oXfWpPJO1jAWeZpdGvJbVypxVFNNxFDFATrG7/JuAkoUJWbYQ28Q DKmHH8DXzyaB+NGA3rLpiAJSy59yNN5YZi/vK5I1fdF2L6uMw9dY3AND+RYSdzFp AXMx7Wg1n8MylxKc45GS6NgzCG1P43BeB0dSsLoxKZMkg7EDjwm7qug6PrebtbI8 Tvk0UEhdzHlXaGFTUrNVW6XrMJG6J9UhmoO2uS/KMUCnG2FsMJSwLPIdigxKqDSu bccFD6tQz4+VkG9KdiEw+/ofXtS5zF9ZiTPf3cETDbcMWQ8Vm47aq49sTOGF6LTt MLtPRRvu32oDg4UN6o1hGhUoiFcF8d2SEIPkDWsKahutOaL4vHw= =uxHW -----END PGP SIGNATURE----- --Mf2CRNBB5HrIBekLkGCVl7fFA28A9J5x4--

3 3

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #143 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Jan '17

08 Jan '17

------=_Part_124_1594460510.1483641357074 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/143/, Build Number: 143, Build Status: FAILURE ------=_Part_124_1594460510.1483641357074--

1 4

oVirt infra daily report - unstable production jobs - 193
by jenkins＠jenkins.phx.ovirt.org 08 Jan '17

08 Jan '17

------=_Part_158_632625730.1483830061682 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/193//artifact/exported-a… Cheers, Jenkins ------=_Part_158_632625730.1483830061682 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 - 07/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/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-system-tests_master_check-patch-fc24-x86…">ovirt-system-tests_master_check-patch-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_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.1_system-tests/">ovirt_4.1_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.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_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.1/">test-repo_ovirt_experimental_4.1</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_158_632625730.1483830061682--

1 0

oVirt infra daily report - unstable production jobs - 192
by jenkins＠jenkins.phx.ovirt.org 07 Jan '17

07 Jan '17

------=_Part_154_1644793575.1483743602243 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/192//artifact/exported-a… Cheers, Jenkins ------=_Part_154_1644793575.1483743602243 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 - 06/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/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_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.1_system-tests/">ovirt_4.1_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.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_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.1/">test-repo_ovirt_experimental_4.1</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_154_1644793575.1483743602243--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4618 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 06 Jan '17

06 Jan '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4615 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 06 Jan '17

06 Jan '17

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

1 1

[JIRA] (OVIRT-1008) ovirt-srv15 unreachable
by Evgheni Dereveanchin (oVirt JIRA) 06 Jan '17

06 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1008?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1008: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > ovirt-srv15 unreachable > ----------------------- > > Key: OVIRT-1008 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1008 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Hosting > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > A short time after ovirt-srv15 (one of the Power8 hypervisors) was updated to CentOS 7.3 it went offline. Opening this case to troubleshoot. It was hosting 16 ppc64le Jenkins slaves. We still have slaves running on ovirt-srv16 so this is not critical at the moment. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1008) ovirt-srv15 unreachable
by Evgheni Dereveanchin (oVirt JIRA) 06 Jan '17

06 Jan '17

Evgheni Dereveanchin created OVIRT-1008: ------------------------------------------- Summary: ovirt-srv15 unreachable Key: OVIRT-1008 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1008 Project: oVirt - virtualization made easy Issue Type: Outage Components: Hosting Reporter: Evgheni Dereveanchin Assignee: infra A short time after ovirt-srv15 (one of the Power8 hypervisors) was updated to CentOS 7.3 it went offline. Opening this case to troubleshoot. It was hosting 16 ppc64le Jenkins slaves. We still have slaves running on ovirt-srv16 so this is not critical at the moment. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

oVirt infra daily report - unstable production jobs - 191
by jenkins＠jenkins.phx.ovirt.org 06 Jan '17

06 Jan '17

------=_Part_142_1026887199.1483657266837 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/191//artifact/exported-a… Cheers, Jenkins ------=_Part_142_1026887199.1483657266837 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 - 05/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/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_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.1_system-tests/">ovirt_4.1_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.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_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.1/">test-repo_ovirt_experimental_4.1</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_142_1026887199.1483657266837--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4605 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4601 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

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

1 2

Re: [ovirt-users] The feature everyone was asking for is finally here...
by Eyal Edri 05 Jan '17

05 Jan '17

I'm not sure I follow how CLI is related to the job, ost is using the ovirt python sdk to run the tests. On Jan 5, 2017 3:36 PM, "Logan Kuhn" <logank(a)wolfram.com> wrote: > Isn't the CLI going away in the semi-near future? > > Regards, > Logan > > ----- On Jan 4, 2017, at 9:31 AM, Eyal Edri <eedri(a)redhat.com> wrote: > > FYI, > > After many requests from multiple developers and testers, the oVirt CI > added a new simple job that lets you run the full fledged end-to-end oVirt > system tests with a click of a button. > You can read all the details and how-to in the new oVirt blog [1]. > > We wanted to allow running oVirt system tests on EVERY open patch from ANY > oVirt project, without relaying on complex building code inside the job. > Luckily we just added the 'build-on-demand' so together with it you can > build any rpms you'd like and use them to run the manual job. > > So the 2 steps you'll need to do are: > > 1. Write 'ci please build' inside a comment on an open oVirt patch ( > make sure the feature is enabled for that project first, its already > available for ovirt-engine,vdsm,dashboard and vdsm-jsonrpc-java) > 2. Run the manual OST job for the version you'd like to test with the > URLs you got from #1 > > You'll get and email once the job is done and you can browse the results > and check for logs from engine and the hosts. > > Please feel free to ask questions on infra(a)ovirt.org as usual. > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > >

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #140 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

------=_Part_120_1545252879.1483634764629 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/140/, Build Number: 140, Build Status: FAILURE ------=_Part_120_1545252879.1483634764629--

1 1