- Devel - oVirt List Archives

Re: [Engine-devel] May I apply for a user account on jenkins.ovirt.org to run VDSM functional tests?
by Eyal Edri 29 Jan '13

29 Jan '13

----- Original Message ----- > From: "Zhou Zheng Sheng" <zhshzhou(a)linux.vnet.ibm.com> > To: infra(a)ovirt.org > Cc: "ShaoHe Feng" <shaohef(a)linux.vnet.ibm.com> > Sent: Tuesday, January 29, 2013 12:24:27 PM > Subject: May I apply for a user account on jenkins.ovirt.org to run VDSM functional tests? > > Hi all, > > I notice there is no VDSM functional tests running in oVirt Jenkins. > Currently in VDSM we have some XML-RPC functional test cases for > iSCSI, > localfs and glusterfs storage as well as creating and destroying VMs > on > those storage. Functional tests through JSON-RPC are under review. I > also submit a patch to Gerrit for running the tests easily > (http://gerrit.ovirt.org/#/c/11238/) More test cases will be added > to > improve test coverage and reduce the chance of regression. > > Some bugs that can not be covered by unit test can be caught by > functional tests. I think it would be helpful to run these functional > tests continuously. We can also configure the Gerrit trigger in > Jenkins > to run functional tests when someone verifies the patch or when it > gets > approved but not merged. This may be helpful to the maintainer. > > I've setup a Jenkins job for VDSM functional tests in my lab server. > You > can refer to the job configuration of my current setup > (https://github.com/edwardbadboy/vdsm-jenkins/blob/master/config.xml) > After my patch in Gerrit is accepted, the job configuration will be > simpler and the hacks can be removed. May I apply a user account for > creating job in the oVirt Jenkins? > Hi Zhou, Basically there shouldn't be any problem with that. we have an option for giving a 'power-user' permissions for certain users on oVirt misc projects to add and and configure jobs for thier project. it requires knowledge in jenkins, which it seems that you have and recognition from the team/other developers from the relevant project (in this case, VDSM) that you are an active member of the project. (just a formality essentially) I've added engine-devel list to this thread so anyone from vdsm team can vote +1 for adding you as a power user for jenkins. once we'll receive a few +1 and not objections i'll create a user for you and send you the details. you'll be able to: 1. create new jobs 2. update jobs configurations 3. run jobs.. > -- > Thanks and best regards! > > Zhou Zheng Sheng / 周征晟 > E-mail: zhshzhou(a)linux.vnet.ibm.com > Telephone: 86-10-82454397 > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra >

2 1

[Engine-devel] Change in the RPM release
by Juan Hernandez 29 Jan '13

29 Jan '13

Hello all, I have just merged a patch (see [1]) into the master branch that changes how the release number of RPMs is created by default. Now it will be like this: 0.1.$(date +%Y%m%d%H%M%S) This may impact you if you are building your own RPMs, but only if you are not explicitly forcing the release number with something like this: make rpm RPM_RELEASE_VERSION=whatever [1] http://gerrit.ovirt.org/9704 Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

1 0

[Engine-devel] [JENKINS] important change in findbugs analysis
by Eyal Edri 27 Jan '13

27 Jan '13

fyi, as part of the efforts to reduce bugs found by findbugs jenkins job, NORMAL priority bugs limit has been set to 15 (current count), this means that any NEW NORMAL bugs that will enter ovirt-engine code will fail the job, and it's the committer responsibility to fix it. if you're not sure about your code, you can run mvn findbugs:findbugs before merging (there's also an eclipse plugin for it). there is on-going work on reducing NORMAL bugs, and this limit will reduce in the near future, until it will reach '0' (similar to HIGH prirority). thanks for the cooperation. Eyal Edri oVirt infra team.

1 0

Re: [Engine-devel] [oVirt Jenkins] ovirt_engine_unit_tests - Build # 3216 - Still unstable!
by Eyal Edri 27 Jan '13

27 Jan '13

fyi, seems like this patch introduced new unit test failure, please check, http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git&a=commit&h=207cda518399d0… http://jenkins.ovirt.org/job/ovirt_engine_unit_tests/3212/ Eyal. Infra team. ----- Original Message ----- > From: "Jenkins oVirt Server" <jenkins(a)ovirt.org> > To: eedri(a)redhat.com, engine-patches(a)ovirt.org, oliel(a)redhat.com, yzaslavs(a)redhat.com > Sent: Friday, January 25, 2013 11:49:10 AM > Subject: [oVirt Jenkins] ovirt_engine_unit_tests - Build # 3216 - Still unstable! > > Project: http://jenkins.ovirt.org/job/ovirt_engine_unit_tests/ > Build: http://jenkins.ovirt.org/job/ovirt_engine_unit_tests/3216/ > Build Number: 3216 > Build Status: Still unstable > Triggered By: Started by upstream project "ovirt_engine" build number > 4,107, Started by upstream project "ovirt_engine" build number 4,109 > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #3212 > [gerrit2] engine: consolidate VM and Poll queries > > > Changes for Build #3213 > [gerrit2] core:unlock_entity.sh is not finding a locked ... > > [gerrit2] core:unlock_entity.sh is not unlocking the vm... > > [emesika] core:If no power management configured or fails... > > > Changes for Build #3214 > > Changes for Build #3215 > [gerrit2] packaging: Starting ssh before adding host in AIO > > [gerrit2] packaging: Updated spec to use sdk version that supports > ssl. > > [gerrit2] spelling: s/mster/master/ > > > Changes for Build #3216 > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: > org.ovirt.engine.core.bll.GetAllVmPoolsAttachedToUserQueryTest.testQueryIsAUserQuery > > Error Message: > A query tested for filtered access should not be an admin query > > Stack Trace: > java.lang.AssertionError: A query tested for filtered access should > not be an admin query > at org.junit.Assert.fail(Assert.java:93) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.junit.Assert.assertFalse(Assert.java:68) > at > org.ovirt.engine.core.bll.AbstractUserQueryTest.testQueryIsAUserQuery(AbstractUserQueryTest.java:58) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at > org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > > > > > ------------------ > Build Log: > ------------------ > [...truncated 6074 lines...] > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/maven-artifact-manager/2.0.8… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/maven-artifact-manager/2.0.8… > (3 KB at 164.8 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/maven-repository-metadata/2.… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/maven-repository-metadata/2.… > (2 KB at 142.8 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-registry/2.0.8/… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-registry/2.0.8/… > (2 KB at 57.4 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-common-artifact… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-common-artifact… > (2 KB at 164.0 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-im… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-im… > (2 KB at 164.0 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting/2.… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting/2.… > (700 B at 25.3 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-core/1.0-alpha-7… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-core/1.0-alpha-7… > (2 KB at 109.7 KB/sec) > Downloading: > http://repo1.maven.org/maven2/oro/oro/2.0.7/oro-2.0.7.pom > Downloaded: http://repo1.maven.org/maven2/oro/oro/2.0.7/oro-2.0.7.pom > (141 B at 9.8 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-ap… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-ap… > (902 B at 80.1 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.… > (2 KB at 127.6 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.2/ple… > Downloaded: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.2/ple… > (8 KB at 570.5 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-default/… > Downloaded: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container-default/… > (2 KB at 104.9 KB/sec) > Downloading: > http://repo1.maven.org/maven2/plexus/plexus-containers/1.0.2/plexus-contain… > Downloaded: > http://repo1.maven.org/maven2/plexus/plexus-containers/1.0.2/plexus-contain… > (471 B at 38.3 KB/sec) > Downloading: > http://repo1.maven.org/maven2/plexus/plexus-root/1.0.3/plexus-root-1.0.3.pom > Downloaded: > http://repo1.maven.org/maven2/plexus/plexus-root/1.0.3/plexus-root-1.0.3.pom > (6 KB at 489.8 KB/sec) > Downloading: > http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.… > Downloaded: > http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.… > (740 B at 60.2 KB/sec) > Downloading: > http://repo1.maven.org/maven2/commons-logging/commons-logging-api/1.0.4/com… > Downloaded: > http://repo1.maven.org/maven2/commons-logging/commons-logging-api/1.0.4/com… > (168 B at 13.7 KB/sec) > Downloading: > http://repo1.maven.org/maven2/velocity/velocity/1.4/velocity-1.4.pom > Downloaded: > http://repo1.maven.org/maven2/velocity/velocity/1.4/velocity-1.4.pom > (3 KB at 174.3 KB/sec) > Downloading: > http://repo1.maven.org/maven2/velocity/velocity-dep/1.4/velocity-dep-1.4.pom > Downloaded: > http://repo1.maven.org/maven2/velocity/velocity-dep/1.4/velocity-dep-1.4.pom > (2 KB at 154.3 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model… > (2 KB at 99.0 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.6/plexus… > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-shared-io/1.0/m… > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-dependency-anal… > Downloaded: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.4.6/plexus… > (200 KB at 6431.1 KB/sec) > Downloading: http://repo1.maven.org/maven2/asm/asm/3.0/asm-3.0.jar > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-shared-io/1.0/m… > (33 KB at 1052.7 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-common-artifact… > Downloaded: http://repo1.maven.org/maven2/asm/asm/3.0/asm-3.0.jar (42 > KB at 2085.4 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-im… > Downloading: > http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/c… > Downloading: > http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-common-artifact… > (27 KB at 1565.7 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-core/1.0-alpha-7… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-im… > (14 KB at 833.5 KB/sec) > Downloading: > http://repo1.maven.org/maven2/oro/oro/2.0.7/oro-2.0.7.jar > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/shared/maven-dependency-anal… > (27 KB at 400.2 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.… > Downloaded: http://repo1.maven.org/maven2/oro/oro/2.0.7/oro-2.0.7.jar > (64 KB at 1936.1 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.2/ple… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-core/1.0-alpha-7… > (226 KB at 6274.1 KB/sec) > Downloading: > http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.… > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.… > (13 KB at 538.3 KB/sec) > Downloading: > http://repo1.maven.org/maven2/commons-logging/commons-logging-api/1.0.4/com… > Downloaded: > http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons… > (38 KB at 675.0 KB/sec) > Downloading: > http://repo1.maven.org/maven2/velocity/velocity/1.4/velocity-1.4.jar > Downloaded: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.2/ple… > (8 KB at 222.3 KB/sec) > Downloading: > http://repo1.maven.org/maven2/velocity/velocity-dep/1.4/velocity-dep-1.4.jar > Downloaded: > http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.… > (157 KB at 3915.6 KB/sec) > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model… > Downloaded: > http://repo1.maven.org/maven2/commons-logging/commons-logging-api/1.0.4/com… > (26 KB at 673.4 KB/sec) > Downloaded: > http://repo1.maven.org/maven2/commons-collections/commons-collections/2.1/c… > (162 KB at 1645.4 KB/sec) > Downloaded: > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model… > (38 KB at 2193.0 KB/sec) > Downloaded: > http://repo1.maven.org/maven2/velocity/velocity/1.4/velocity-1.4.jar > (353 KB at 4898.7 KB/sec) > Downloaded: > http://repo1.maven.org/maven2/velocity/velocity-dep/1.4/velocity-dep-1.4.jar > (506 KB at 10758.0 KB/sec) > [INFO] Configured Artifact: org.quartz-scheduler:quartz:2.1.2:jar > [INFO] Copying quartz-2.1.2.jar to > /home/jenkins/workspace/ovirt_engine_unit_tests/ear/target/quartz/quartz-2.1.2.jar > mojoSucceeded > org.apache.maven.plugins:maven-dependency-plugin:2.1(copy-quartz-jar) > [INFO] Installing > /home/jenkins/workspace/ovirt_engine_unit_tests/ear/target/engine.ear > to > /home/jenkins/workspace/ovirt_engine_unit_tests/.repository/org/ovirt/engine/engine-server-ear/3.2.0/engine-server-ear-3.2.0.ear > mojoStarted > org.apache.maven.plugins:maven-install-plugin:2.3.1(default-install) > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > engine-server-ear --- > [INFO] Installing > /home/jenkins/workspace/ovirt_engine_unit_tests/ear/pom.xml to > /home/jenkins/workspace/ovirt_engine_unit_tests/.repository/org/ovirt/engine/engine-server-ear/3.2.0/engine-server-ear-3.2.0.pom > mojoSucceeded > org.apache.maven.plugins:maven-install-plugin:2.3.1(default-install) > projectSucceeded org.ovirt.engine:engine-server-ear:3.2.0 > sessionEnded > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] ovirt-root ........................................ SUCCESS > [8.538s] > [INFO] oVirt Build Tools root ............................ SUCCESS > [0.238s] > [INFO] oVirt checkstyle .................................. SUCCESS > [6.895s] > [INFO] oVirt Checkstyle Checks ........................... SUCCESS > [2.763s] > [INFO] oVirt Modules - backend ........................... SUCCESS > [0.246s] > [INFO] oVirt Manager ..................................... SUCCESS > [0.234s] > [INFO] oVirt DB Scripts .................................. SUCCESS > [0.950s] > [INFO] oVirt Modules - manager ........................... SUCCESS > [6.026s] > [INFO] CSharp Compatibility .............................. SUCCESS > [14.711s] > [INFO] Encryption Libraries .............................. SUCCESS > [5.150s] > [INFO] oVirt Tools ....................................... SUCCESS > [0.619s] > [INFO] oVirt Tools Common Library ........................ SUCCESS > [4.614s] > [INFO] Common Code ....................................... SUCCESS > [28.455s] > [INFO] Common utilities .................................. SUCCESS > [32.168s] > [INFO] Data Access Layer ................................. SUCCESS > [30.996s] > [INFO] engine beans ...................................... SUCCESS > [0.304s] > [INFO] engine scheduler bean ............................. SUCCESS > [5.388s] > [INFO] Vds broker ........................................ SUCCESS > [14.906s] > [INFO] Search Backend .................................... SUCCESS > [8.260s] > [INFO] Backend Logic @Service bean ....................... SUCCESS > [1:16.188s] > [INFO] oVirt RESTful API Backend Integration ............. SUCCESS > [8.478s] > [INFO] oVirt RESTful API interface ....................... SUCCESS > [0.334s] > [INFO] oVirt Engine API Definition ....................... SUCCESS > [25.865s] > [INFO] oVirt Engine API Commom Parent POM ................ SUCCESS > [0.311s] > [INFO] oVirt Engine API Common JAX-RS .................... SUCCESS > [17.147s] > [INFO] oVirt RESTful API Backend Integration Type Mappers SUCCESS > [51.144s] > [INFO] oVirt RESTful API Backend Integration JAX-RS Resources > SUCCESS [54.674s] > [INFO] oVirt RESTful API Backend Integration Webapp ...... SUCCESS > [2.285s] > [INFO] oVirt Engine Web Root ............................. SUCCESS > [2.731s] > [INFO] oVirt Configuration Tool .......................... SUCCESS > [3.816s] > [INFO] Notifier Service package .......................... SUCCESS > [0.171s] > [INFO] Notifier Service .................................. SUCCESS > [4.180s] > [INFO] Notifier Service Resources ........................ SUCCESS > [2.233s] > [INFO] oVirt Modules :: Frontend ......................... SUCCESS > [0.182s] > [INFO] oVirt Modules :: Webadmin ......................... SUCCESS > [0.187s] > [INFO] oVirt Modules - ui ................................ SUCCESS > [0.185s] > [INFO] Extensions for GWT ................................ SUCCESS > [4.740s] > [INFO] UI Utils Compatibility (for UICommon) ............. SUCCESS > [6.985s] > [INFO] Frontend for GWT UI Projects ...................... SUCCESS > [6.357s] > [INFO] UICommonWeb ....................................... SUCCESS > [27.230s] > [INFO] oVirt GWT UI common infrastructure ................ SUCCESS > [33.023s] > [INFO] WebAdmin .......................................... SUCCESS > [28.203s] > [INFO] UserPortal ........................................ SUCCESS > [12.630s] > [INFO] oVirt WARs ........................................ SUCCESS > [0.165s] > [INFO] oVirt Web Application Module ...................... SUCCESS > [2.619s] > [INFO] oVirt Server EAR .................................. SUCCESS > [8.673s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 9:19.320s > [INFO] Finished at: Fri Jan 25 04:49:19 EST 2013 > [INFO] Final Memory: 319M/676M > [INFO] > ------------------------------------------------------------------------ > Projects to build: [MavenProject: org.ovirt.engine:root:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/pom.xml, > MavenProject: org.ovirt.engine:build-tools-root:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/pom.xml, > MavenProject: org.ovirt.engine:checkstyles:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/checkstyles/pom.xml, > MavenProject: org.ovirt.engine:ovirt-checkstyle-extension:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/ovirt-checkstyle-extension/pom.xml, > MavenProject: org.ovirt.engine.core:backend:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/pom.xml, > MavenProject: org.ovirt.engine.core:manager:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/pom.xml, > MavenProject: org.ovirt.engine.core:dbscripts:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/dbscripts/pom.xml, > MavenProject: org.ovirt.engine.core:manager-modules:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/pom.xml, > MavenProject: org.ovirt.engine.core:compat:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/compat/pom.xml, > MavenProject: org.ovirt.engine.core:engineencryptutils:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/engineencryptutils/pom.xml, > MavenProject: org.ovirt.engine.core:manager-tools:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/pom.xml, > MavenProject: org.ovirt.engine.core:engine-tools-common:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-tools-common/pom.xml, > MavenProject: org.ovirt.engine.core:common:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/common/pom.xml, > MavenProject: org.ovirt.engine.core:utils:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/utils/pom.xml, > MavenProject: org.ovirt.engine.core:dal:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/dal/pom.xml, > MavenProject: org.ovirt.engine.core:beans:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/beans/pom.xml, > MavenProject: org.ovirt.engine.core:scheduler:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/beans/scheduler/pom.xml, > MavenProject: org.ovirt.engine.core:vdsbroker:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/vdsbroker/pom.xml, > MavenProject: org.ovirt.engine.core:searchbackend:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/searchbackend/pom.xml, > MavenProject: org.ovirt.engine.core:bll:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/bll/pom.xml, > MavenProject: org.ovirt.engine.api:restapi-parent:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/pom.xml, > MavenProject: org.ovirt.engine.api:interface:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/pom.xml, > MavenProject: org.ovirt.engine.api:restapi-definition:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/definition/pom.xml, > MavenProject: org.ovirt.engine.api:common-parent:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/common/pom.xml, > MavenProject: org.ovirt.engine.api:interface-common-jaxrs:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/common/jaxrs/pom.xml, > MavenProject: org.ovirt.engine.api:restapi-types:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/types/pom.xml, > MavenProject: org.ovirt.engine.api:restapi-jaxrs:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/jaxrs/pom.xml, > MavenProject: org.ovirt.engine.api:restapi-webapp:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/webapp/pom.xml, > MavenProject: org.ovirt.engine.core:root-war:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/root/pom.xml, > MavenProject: org.ovirt.engine.core:engine-config:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-config/pom.xml, > MavenProject: org.ovirt.engine.core:engine-notifier:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/pom.xml, > MavenProject: org.ovirt.engine.core:engine-notifier-service:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-service/pom.xml, > MavenProject: org.ovirt.engine.core:engine-notifier-resources:3.2.0 > @ > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-resources/pom.xml, > MavenProject: org.ovirt.engine.ui:frontend-all:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/pom.xml, > MavenProject: org.ovirt.engine.ui:webadmin-all:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/pom.xml, > MavenProject: org.ovirt.engine.ui:webadmin-modules:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/pom.xml, > MavenProject: org.ovirt.engine.ui:gwt-extension:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-extension/pom.xml, > MavenProject: org.ovirt.engine.ui:uicompat:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicompat/pom.xml, > MavenProject: org.ovirt.engine.ui:frontend:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/frontend/pom.xml, > MavenProject: org.ovirt.engine.ui:uicommonweb:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicommonweb/pom.xml, > MavenProject: org.ovirt.engine.ui:gwt-common:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-common/pom.xml, > MavenProject: org.ovirt.engine.ui:webadmin:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/webadmin/pom.xml, > MavenProject: org.ovirt.engine.ui:userportal:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/userportal-gwtp/pom.xml, > MavenProject: org.ovirt.engine.ui:wars:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/wars/pom.xml, > MavenProject: org.ovirt.engine.ui:rmw-war:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/wars/rmw-war/pom.xml, > MavenProject: org.ovirt.engine:engine-server-ear:3.2.0 @ > /home/jenkins/workspace/ovirt_engine_unit_tests/ear/pom.xml] > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/beans/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicommonweb/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicommonweb/target/uicommonweb-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicommonweb/target/uicommonweb-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicommonweb/target/uicommonweb-3.2.0-sources.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/root/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/root/target/root-war-3.2.0.war > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/webapp/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/webapp/target/restapi-webapp-3.2.0.war > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-tools-common/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-tools-common/target/engine-tools-common-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-tools-common/target/engine-tools-common-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/common/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/common/target/common-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/common/target/common-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/common/target/common-3.2.0-sources.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-common/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-common/target/gwt-common-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-common/target/gwt-common-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/wars/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/checkstyles/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/checkstyles/target/checkstyles-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/checkstyles/target/checkstyles-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/beans/scheduler/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/beans/scheduler/target/scheduler-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/beans/scheduler/target/scheduler-3.2.0-client.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-resources/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-resources/target/engine-notifier-resources-3.2.0.zip > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-config/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-config/target/engine-config-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-config/target/engine-config-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/engineencryptutils/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/engineencryptutils/target/engineencryptutils-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/engineencryptutils/target/engineencryptutils-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-service/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-service/target/engine-notifier-service-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/tools/engine-notifier/engine-notifier-service/target/engine-notifier-service-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/utils/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/utils/target/utils-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/utils/target/utils-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/common/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/definition/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/definition/target/restapi-definition-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/definition/target/restapi-definition-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/types/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/types/target/restapi-types-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/types/target/restapi-types-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicompat/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicompat/target/uicompat-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/uicompat/target/uicompat-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/ovirt-checkstyle-extension/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/ovirt-checkstyle-extension/target/ovirt-checkstyle-extension-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/ovirt-checkstyle-extension/target/ovirt-checkstyle-extension-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/jaxrs/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/jaxrs/target/restapi-jaxrs-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/jaxrs/target/restapi-jaxrs-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/frontend/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/frontend/target/frontend-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/frontend/target/frontend-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/wars/rmw-war/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/wars/rmw-war/target/rmw-war-3.2.0.war > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/dal/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/dal/target/dal-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/dal/target/dal-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/ear/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/ear/target/engine.ear > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/webadmin/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/webadmin/target/webadmin-3.2.0.war > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/searchbackend/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/searchbackend/target/searchbackend-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/searchbackend/target/searchbackend-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/searchbackend/target/searchbackend-3.2.0-sources.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-extension/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-extension/target/gwt-extension-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-extension/target/gwt-extension-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/gwt-extension/target/gwt-extension-3.2.0-sources.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/build-tools-root/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/compat/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/compat/target/compat-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/compat/target/compat-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/compat/target/compat-3.2.0-sources.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/common/jaxrs/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/common/jaxrs/target/interface-common-jaxrs-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/restapi/interface/common/jaxrs/target/interface-common-jaxrs-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/userportal-gwtp/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/frontend/webadmin/modules/userportal-gwtp/target/userportal-3.2.0.war > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/vdsbroker/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/vdsbroker/target/vdsbroker-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/vdsbroker/target/vdsbroker-3.2.0-tests.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/bll/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/bll/target/bll-3.2.0.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/modules/bll/target/bll-3.2.0-client.jar > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/pom.xml > [JENKINS] Archiving disabled - not archiving > /home/jenkins/workspace/ovirt_engine_unit_tests/backend/manager/dbscripts/pom.xml > Waiting for Jenkins to finish collecting data > channel stopped > IRC notifier plugin: Sending notification to: #ovirt-jenkins > Email was triggered for: Unstable > Sending email for trigger: Unstable >

2 1

[Engine-devel] default Vm memory size
by Laszlo Hornyak 24 Jan '13

24 Jan '13

Hi, The default Vm size is 512 MB now. I think A bit more could be useful, e.g. a fedora installer won't start with 512 MB. What about 1024 MB? thx, Laszlo

4 3

[Engine-devel] ovirt engine sdk
by navin p 23 Jan '13

23 Jan '13

Hi, I've written the following python program after configuring ovirt. from ovirtsdk.xml import params from ovirtsdk.api import API api=API(url='http://XYZ:80',username='ABC',password='123') print "\n**********************VMS************************\n" vmlist = api.vms.list() hostlist = api.hosts.list() evenlist = api.events.list(); for vm in vmlist: print vm.name,vm.memory,vm.id,vm.os.kernel,vm.cluster.id,vm.start_time print "\n**********************HOSTS ********************\n" for host in hostlist: print host.name #print "\n**********************EVENTS ********************\n" #for evt in evenlist: # print evt.description It prints the output as *********************VMS************************ fedora18 2147483648 3e4634b7-82a9-4c4f-8599-0f9092a9258e None 99408929-82cf-4dc7-a532-9d998063fa95 None testdtop1 536870912 c256a1d9-2e3f-42e8-9020-6d08d21d2d73 None 99408929-82cf-4dc7-a532-9d998063fa95 2013-01-23T09:59:36.726Z testvm1 268435456 f6b2a97d-34b2-4a62-adae-ac0504b96558 None 99408929-82cf-4dc7-a532-9d998063fa95 2013-01-23T09:55:06.727Z testvmfedora18 536870912 25c14ee6-65dd-4785-af0c-a8df3f87573f None 99408929-82cf-4dc7-a532-9d998063fa95 None **********************HOSTS ******************** omwin.ind.hp.com Now i want to get the statistics for each vm like the memory used and memory installed etc in python. How do i go about getting them ? Do we have something like a header file in C or C++ where i can see the member variables and then get the statistics ? Regards, Navin

2 3

[Engine-devel] ovirt node
by David Michel (ODEC Ltd.) 23 Jan '13

23 Jan '13

hi i cannot add ovirt node to ovirt-engine ssh error occur although i can connect to the node using ssh from engine machine please i need your help to solve this issue thanks

2 1

[Engine-devel] RFC: New Storage API
by Saggi Mizrahi 22 Jan '13

22 Jan '13

I've been throwing a lot of bits out about the new storage API and I think it's time to talk a bit. I will purposefully try and keep implementation details away and concentrate about how the API looks and how you use it. First major change is in terminology, there is no long a storage domain but a storage repository. This change is done because so many things are already called domain in the system and this will make things less confusing for new-commers with a libvirt background. One other changes is that repositories no longer have a UUID. The UUID was only used in the pool members manifest and is no longer needed. connectStorageRepository(repoId, repoFormat, connectionParameters={}): repoId - is a transient name that will be used to refer to the connected domain, it is not persisted and doesn't have to be the same across the cluster. repoFormat - Similar to what used to be type (eg. localfs-1.0, nfs-3.4, clvm-1.2). connectionParameters - This is format specific and will used to tell VDSM how to connect to the repo. disconnectStorageRepository(self, repoId): In the new API there are only images, some images are mutable and some are not. mutable images are also called VirtualDisks immutable images are also called Snapshots There are no explicit templates, you can create as many images as you want from any snapshot. There are 4 major image operations: createVirtualDisk(targetRepoId, size, baseSnapshotId=None, userData={}, options={}): targetRepoId - ID of a connected repo where the disk will be created size - The size of the image you wish to create baseSnapshotId - the ID of the snapshot you want the base the new virtual disk on userData - optional data that will be attached to the new VD, could be anything that the user desires. options - options to modify VDSMs default behavior returns the id of the new VD createSnapshot(targetRepoId, baseVirtualDiskId, userData={}, options={}): targetRepoId - The ID of a connected repo where the new sanpshot will be created and the original image exists as well. size - The size of the image you wish to create baseVirtualDisk - the ID of a mutable image (Virtual Disk) you want to snapshot userData - optional data that will be attached to the new Snapshot, could be anything that the user desires. options - options to modify VDSMs default behavior returns the id of the new Snapshot copyImage(targetRepoId, imageId, baseImageId=None, userData={}, options={}) targetRepoId - The ID of a connected repo where the new image will be created imageId - The image you wish to copy baseImageId - if specified, the new image will contain only the diff between image and Id. If None the new image will contain all the bits of image Id. This can be used to copy partial parts of images for export. userData - optional data that will be attached to the new image, could be anything that the user desires. options - options to modify VDSMs default behavior return the Id of the new image. In case of copying an immutable image the ID will be identical to the original image as they contain the same data. However the user should not assume that and always use the value returned from the method. removeImage(repositoryId, imageId, options={}): repositoryId - The ID of a connected repo where the image to delete resides imageId - The id of the image you wish to delete. ---- getImageStatus(repositoryId, imageId) repositoryId - The ID of a connected repo where the image to check resides imageId - The id of the image you wish to check. All operations return once the operations has been committed to disk NOT when the operation actually completes. This is done so that: - operation come to a stable state as quickly as possible. - In case where there is an SDM, only small portion of the operation actually needs to be performed on the SDM host. - No matter how many times the operation fails and on how many hosts, you can always resume the operation and choose when to do it. - You can stop an operation at any time and remove the resulting object making a distinction between "stop because the host is overloaded" to "I don't want that image" This means that after calling any operation that creates a new image the user must then call getImageStatus() to check what is the status of the image. The status of the image can be either optimized, degraded, or broken. "Optimized" means that the image is available and you can run VMs of it. "Degraded" means that the image is available and will run VMs but it might be a better way VDSM can represent the underlying data. "Broken" means that the image can't be used at the moment, probably because not all the data has been set up on the volume. Apart from that VDSM will also return the last persisted status information which will conatin hostID - the last host to try and optimize of fix the image stage - X/Y (eg. 1/10) the last persisted stage of the fix. percent_complete - -1 or 0-100, the last persisted completion percentage of the aforementioned stage. -1 means that no progress is available for that operation. last_error - This will only be filled if the operation failed because of something other then IO or a VDSM crash for obvious reasons. It will usually be set if the task was manually stopped The user can either be satisfied with that information or as the host specified in host ID if it is still working on that image by checking it's running tasks. checkStorageRepository(self, repositoryId, options={}): A method to go over a storage repository and scan for any existing problems. This includes degraded\broken images and deleted images that have no yet been physically deleted\merged. It returns a list of Fix objects. Fix objects come in 4 types: clean - cleans data, run them to get more space. optimize - run them to optimize a degraded image merge - Merges two images together. Doing this sometimes makes more images ready optimizing or cleaning. The reason it is different from optimize is that unmerged images are considered optimized. mend - mends a broken image The user can read these types and prioritize fixes. Fixes also contain opaque FIX data and they should be sent as received to fixStorageRepository(self, repositoryId, fix, options={}): That will start a fix operation. All major operations automatically start the appropriate "Fix" to bring the created object to an optimize\degraded state (the one that is quicker) unless one of the options is AutoFix=False. This is only useful for repos that might not be able to create volumes on all hosts (SDM) but would like to have the actual IO distributed in the cluster. Other common options is the strategy option: It has currently 2 possible values space and performance - In case VDSM has 2 ways of completing the same operation it will tell it to value one over the other. For example, whether to copy all the data or just create a qcow based of a snapshot. The default is space. You might have also noticed that it is never explicitly specified where to look for existing images. This is done purposefully, VDSM will always look in all connected repositories for existing objects. For very large setups this might be problematic. To mitigate the problem you have these options: participatingRepositories=[repoId, ...] which tell VDSM to narrow the search to just these repositories and imageHints={imgId: repoId} which will force VDSM to look for those image ID just in those repositories and fail if it doesn't find them there.

6 30

[Engine-devel] maven build trick
by Laszlo Hornyak 22 Jan '13

22 Jan '13

hi, I recommend that you add this script to your build script: rm -rf ~/.m2/repository/org/ovirt This will remove the generated ovirt artifacts from your local maven repo. Why is this needed: If you remove some artifact from the build, that other artifacts are built on, these artifacts will still be able to resolve the missing dependency from the local repo (which is wrong). In this way, your build can still depend on an outdated artifact without breaking the build. This is why you do not notice that the build is broken, maven will just take it as a third party artifact. Thx, Laszlo

2 1

[Engine-devel] RFE: Health Indication on UI
by Shireesh Anjal 22 Jan '13

22 Jan '13

Hi, Currently, oVirt is intelligent to understand the relationship hierarchies of various entities in the system, and even allows setting permissions based on this hierarchy. Can this information further be used to enhance the health monitoring of various entities in the system? Let me take an example. Consider this hierarchy (gluster): System -> Cluster -> Volume -> Brick If one or more bricks of a volume are down, which indicates a problem, following entities should be overlaid with a warning symbol (say, a yellow exclamation mark) - Volume to which the brick(s) belong(s) - it's parent cluster - System This helps in highlighting what parts of the system are affected by failures/problems at the lowest level entities, and gives a better idea of the overall health of the entire environment to the administrator. Thoughts? Thanks, Shireesh

2 1