- Devel - oVirt List Archives

Re: [Engine-devel] [oVirt Jenkins] ovirt_engine_dao_unit_tests - Build # 1208 - Still Failing!
by Eyal Edri 12 Jun '12

12 Jun '12

Hi, It seems commit [sesubram] engine: Adding brick order to Gluster volume bricks added new failed dao test: org.ovirt.engine.core.dao.gluster.GlusterBrickDaoTest.testReplaceBrick > > Error Message: > Required input parameter 'v_new_brick_dir' is missing Can you please check? Eyal Edri oVirt 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, mkolesni(a)redhat.com > Sent: Tuesday, June 12, 2012 10:47:31 AM > Subject: [oVirt Jenkins] ovirt_engine_dao_unit_tests - Build # 1208 - Still Failing! > > Project: http://jenkins.ovirt.org/job/ovirt_engine_dao_unit_tests/ > Build: http://jenkins.ovirt.org/job/ovirt_engine_dao_unit_tests/1208/ > Build Number: 1208 > Build Status: Still Failing > Triggered By: Started by upstream project "ovirt_engine" build number > 1,611, Started by upstream project "ovirt_engine" build number > 1,612, Started by upstream project "ovirt_engine" build number 1,613 > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #1191 > [mkublin] core: Disable global transaction at InitVdsOnUp > > [sesubram] engine: Adding brick order to Gluster volume bricks > > > Changes for Build #1192 > > Changes for Build #1193 > [dgopal] restapi: Gluster Volume Bricks resource implementation > > > Changes for Build #1194 > [kmayilsa] engine: Skipping Cluster CPU validation in GlusterOnly > mode > > [kmayilsa] engine: Removing default transport type in volume(#830495) > > > Changes for Build #1195 > [derez] webadmin: display SD status in Storage sub-tab > > [derez] webadmin: Differentiate Virtual/Actual size in disks > > > Changes for Build #1196 > > Changes for Build #1197 > > Changes for Build #1198 > [emesika] core: VMs created by vmpool fail to run(#830789) > > [sesubram] engine: upgrade sql file name sequence number issue fix > > > Changes for Build #1199 > > Changes for Build #1200 > > Changes for Build #1201 > [gchaplik] webadmin: removing uicommon from build (pom) > > > Changes for Build #1202 > > Changes for Build #1203 > [ecohen] ui: fix naming to oVirt Engine > > > Changes for Build #1204 > > Changes for Build #1205 > > Changes for Build #1206 > > Changes for Build #1207 > [yzaslavs] core: Adding new MLA related functions > > [yzaslavs] core: Adding new methods at RoleDAO > > [yzaslavs] common: Introducing groupIds property to VdcUser > > [yzaslavs] core: Preventing adding unauthorized users > > > Changes for Build #1208 > [oliel] restapi: RSDL - Fix meta-data of some collections > > [mkolesni] core: Handle correct NIC ID from OVF (#827061) > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: > org.ovirt.engine.core.dao.gluster.GlusterBrickDaoTest.testReplaceBrick > > Error Message: > Required input parameter 'v_new_brick_dir' is missing > > Stack Trace: > org.springframework.dao.InvalidDataAccessApiUsageException: Required > input parameter 'v_new_brick_dir' is missing > at > org.springframework.jdbc.core.CallableStatementCreatorFactory$CallableStatementCreatorImpl.createCallableStatement(CallableStatementCreatorFactory.java:210) > at > org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:930) > at > org.springframework.jdbc.core.JdbcTemplate.call(JdbcTemplate.java:985) > at > org.springframework.jdbc.core.simple.AbstractJdbcCall.executeCallInternal(AbstractJdbcCall.java:368) > at > org.springframework.jdbc.core.simple.AbstractJdbcCall.doExecute(AbstractJdbcCall.java:342) > at > org.springframework.jdbc.core.simple.SimpleJdbcCall.execute(SimpleJdbcCall.java:164) > at > org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:124) > at > org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeModification(SimpleJdbcCallsHandler.java:37) > at > org.ovirt.engine.core.dao.gluster.GlusterBrickDaoDbFacadeImpl.replaceBrick(GlusterBrickDaoDbFacadeImpl.java:34) > at > org.ovirt.engine.core.dao.gluster.GlusterBrickDaoTest.testReplaceBrick(GlusterBrickDaoTest.java:74) > 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:616) > at > org.springframework.test.context.junit4.SpringTestMethod.invoke(SpringTestMethod.java:160) > at > org.springframework.test.context.junit4.SpringMethodRoadie.runTestMethod(SpringMethodRoadie.java:233) > at > org.springframework.test.context.junit4.SpringMethodRoadie$RunBeforesThenTestThenAfters.run(SpringMethodRoadie.java:333) > at > org.springframework.test.context.junit4.SpringMethodRoadie.runWithRepetitions(SpringMethodRoadie.java:217) > at > org.springframework.test.context.junit4.SpringMethodRoadie.runTest(SpringMethodRoadie.java:197) > at > org.springframework.test.context.junit4.SpringMethodRoadie.run(SpringMethodRoadie.java:143) > at > org.springframework.test.context.junit4.SpringJUnit4ClassRunner.invokeTestMethod(SpringJUnit4ClassRunner.java:160) > at > org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) > at > org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) > at > org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) > at > org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) > at > org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) > at > org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:97) > 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:616) > 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 2719 lines...] > [INFO] Encryption Libraries .............................. SUCCESS > [2.368s] > [INFO] oVirt Tools ....................................... SUCCESS > [0.633s] > [INFO] oVirt Tools Common Library ........................ SUCCESS > [2.004s] > [INFO] Common Code ....................................... SUCCESS > [26.839s] > [INFO] Common utilities .................................. SUCCESS > [9.096s] > [INFO] Data Access Layer ................................. SUCCESS > [14.694s] > [INFO] engine beans ...................................... SUCCESS > [0.122s] > [INFO] engine scheduler bean ............................. SUCCESS > [8.457s] > [INFO] Vds broker ........................................ SUCCESS > [10.079s] > [INFO] Search Backend .................................... SUCCESS > [8.950s] > [INFO] Backend Logic @Service bean ....................... SUCCESS > [33.705s] > [INFO] oVirt RESTful API Backend Integration ............. SUCCESS > [0.621s] > [INFO] oVirt RESTful API interface ....................... SUCCESS > [0.298s] > [INFO] oVirt Engine API Definition ....................... SUCCESS > [9.564s] > [INFO] oVirt Engine API Commom Parent POM ................ SUCCESS > [0.125s] > [INFO] oVirt Engine API Common JAX-RS .................... SUCCESS > [4.601s] > [INFO] oVirt RESTful API Backend Integration Type Mappers SUCCESS > [5.894s] > [INFO] oVirt RESTful API Backend Integration JAX-RS Resources > SUCCESS [16.048s] > [INFO] oVirt RESTful API Backend Integration Webapp ...... SUCCESS > [8.738s] > [INFO] oVirt Engine Web Root ............................. SUCCESS > [4.252s] > [INFO] oVirt Configuration Tool .......................... SUCCESS > [2.756s] > [INFO] Notifier Service package .......................... SUCCESS > [0.128s] > [INFO] Notifier Service .................................. SUCCESS > [3.762s] > [INFO] Notifier Service Resources ........................ SUCCESS > [9.760s] > [INFO] oVirt Modules - frontend .......................... SUCCESS > [0.742s] > [INFO] oVirt APIs ........................................ SUCCESS > [1.084s] > [INFO] oVirt generic API ................................. SUCCESS > [14.910s] > [INFO] oVirt Modules - webadmin .......................... SUCCESS > [0.151s] > [INFO] oVirt Modules - ui ................................ SUCCESS > [0.155s] > [INFO] Extensions for GWT ................................ SUCCESS > [17.891s] > [INFO] UI Utils Compatibility (for UICommon) ............. SUCCESS > [2.642s] > [INFO] Frontend for GWT UI Projects ...................... SUCCESS > [6.577s] > [INFO] UICommonWeb ....................................... SUCCESS > [31.817s] > [INFO] oVirt GWT UI common infrastructure ................ SUCCESS > [28.872s] > [INFO] WebAdmin .......................................... SUCCESS > [39.948s] > [INFO] UserPortal ........................................ SUCCESS > [21.221s] > [INFO] oVirt WARs ........................................ SUCCESS > [0.116s] > [INFO] WPF Application Module ............................ SUCCESS > [8.917s] > [INFO] oVirt Web Application Module ...................... SUCCESS > [9.918s] > [INFO] oVirt Server EAR .................................. SUCCESS > [15.338s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 6:46.263s > [INFO] Finished at: Tue Jun 12 03:40:19 EDT 2012 > [INFO] Final Memory: 317M/765M > [INFO] > ------------------------------------------------------------------------ > [ovirt_engine_dao_unit_tests] $ /home/jenkins/tools/3.0.4/bin/mvn -f > backend/manager/modules/dal/pom.xml > -Dmaven.repo.local=/home/jenkins/workspace/ovirt_engine_dao_unit_tests/.repository > test -Penable-dao-tests > -Dengine.db.url.escaped=jdbc:postgresql://localhost/ovirt_engine_dao_unit_tests_1208 > [INFO] Scanning for projects... > [WARNING] > [WARNING] Some problems were encountered while building the effective > model for org.ovirt.engine.core:dal:jar:3.1.0-0001 > [WARNING] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-resources-plugin is missing. @ line > 125, column 15 > [WARNING] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-surefire-plugin is missing. @ line > 181, column 15 > [WARNING] 'build.plugins.plugin.version' for > org.codehaus.mojo:exec-maven-plugin is missing. @ line 145, column > 15 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they > threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer > support building such malformed projects. > [WARNING] > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Data Access Layer 3.1.0-0001 > [INFO] > ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ > dal --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 210 resources > [INFO] Copying 8 resources > [INFO] Copying 9 resources > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) > @ dal --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ > dal --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-checkstyle-plugin:2.6:check (default) @ dal --- > [INFO] Starting audit... > Audit done. > > [INFO] > [INFO] --- maven-resources-plugin:2.5:testResources > (default-testResources) @ dal --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 9 resources > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:testCompile > (default-testCompile) @ dal --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ dal --- > [INFO] Surefire report directory: > /home/jenkins/workspace/ovirt_engine_dao_unit_tests/backend/manager/modules/dal/target/surefire-reports > > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.ovirt.engine.core.dao.StorageServerConnectionDAOTest > log4j:WARN No appenders could be found for logger > (org.springframework.test.context.junit4.SpringJUnit4ClassRunner). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig > for more info. > SLF4J: The requested version 1.5.11 by your slf4j binding is not > compatible with [1.5.5, 1.5.6] > SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for > further details. > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 5.806 sec > Running org.ovirt.engine.core.dao.VmTemplateDAOTest > Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.24 > sec > Running org.ovirt.engine.core.dao.StepDaoTest > Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.13 > sec > Running org.ovirt.engine.core.dao.VmDynamicDAOTest > Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.96 > sec > Running org.ovirt.engine.core.dao.TagDAOTest > Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.984 sec > Running org.ovirt.engine.core.dao.DbFacadeDAOTest > Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 5.933 sec > Running org.ovirt.engine.core.dao.AsyncTaskDAOTest > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.401 > sec > Running org.ovirt.engine.core.dao.DiskImageDAOTest > Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.06 > sec > Running org.ovirt.engine.core.dao.RoleGroupMapDAOTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.394 > sec > Running org.ovirt.engine.core.dao.NetworkClusterDAOTest > Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.496 sec > Running org.ovirt.engine.core.dao.StoragePoolDAOTest > Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 6.172 sec > Running org.ovirt.engine.core.dao.gluster.GlusterBrickDaoTest > Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.81 > sec <<< FAILURE! > Running org.ovirt.engine.core.dao.gluster.GlusterOptionDaoTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.91 > sec > Running org.ovirt.engine.core.dao.gluster.GlusterVolumeDaoTest > Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.059 sec > Running org.ovirt.engine.core.dao.VmStaticDAOTest > Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.329 sec > Running org.ovirt.engine.core.dao.BookmarkDAOTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.208 > sec > Running org.ovirt.engine.core.dao.JobDaoTest > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 2.937 sec > Running org.ovirt.engine.core.dao.ImageDaoTest > Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.345 > sec > Running org.ovirt.engine.core.dao.BaseDiskDaoTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.953 > sec > Running org.ovirt.engine.core.dao.StorageDomainStaticDAOTest > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.04 > sec > Running org.ovirt.engine.core.dao.VmNetworkStatisticsDAOTest > Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.315 > sec > Running org.ovirt.engine.core.dao.InterfaceDAOTest > Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 4.734 sec > Running org.ovirt.engine.core.dao.DiskDaoTest > Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.557 sec > Running org.ovirt.engine.core.dao.VmStatisticsDAOTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.527 > sec > Running org.ovirt.engine.core.dao.GeneralDbDAOTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.455 > sec > Running org.ovirt.engine.core.dao.NetworkDAOTest > Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.583 sec > Running org.ovirt.engine.core.dao.StorageDomainDynamicDAOTest > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.493 > sec > Running org.ovirt.engine.core.dao.VmDAOTest > Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 4.502 sec > Running org.ovirt.engine.core.dao.EventDAOTest > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.485 sec > Running org.ovirt.engine.core.dao.SnapshotDaoTest > Tests run: 34, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.761 sec > Running org.ovirt.engine.core.dao.PermissionDAOTest > Tests run: 45, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.003 sec > Running org.ovirt.engine.core.dao.VdsDynamicDAOTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.431 > sec > Running org.ovirt.engine.core.dao.StorageDomainDAOTest > Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 11.28 sec > Running org.ovirt.engine.core.dao.ImageStorageDomainMapDaoTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.796 > sec > Running org.ovirt.engine.core.dao.DiskLunMapDaoTest > Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.18 > sec > Running org.ovirt.engine.core.dao.MultiThreadedDAOTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.503 > sec > Running org.ovirt.engine.core.dao.ActionGroupDAOTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.238 > sec > Running org.ovirt.engine.core.dao.VmNetworkInterfaceDAOTest > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 2.875 sec > Running org.ovirt.engine.core.dao.DiskImageDynamicDAOTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.645 > sec > Running org.ovirt.engine.core.dao.VdsSpmIdMapDAOTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.719 > sec > Running org.ovirt.engine.core.dao.VmDeviceDAOTest > Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 4.664 sec > Running org.ovirt.engine.core.dao.AuditLogDAOTest > Tests run: 22, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4 > sec > Running org.ovirt.engine.core.dao.BusinessEntitySnapshotDAOTest > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.824 > sec > Running org.ovirt.engine.core.dao.VdsStatisticsDAOTest > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.13 > sec > Running org.ovirt.engine.core.dao.VdsGroupDAOTest > Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.59 > sec > Running org.ovirt.engine.core.dao.JobSubjectEntityDaoTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.141 > sec > Running org.ovirt.engine.core.dao.LunDAOTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.45 > sec > Running org.ovirt.engine.core.dao.VdsDAOTest > Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 4.168 sec > Running org.ovirt.engine.core.dao.VdsStaticDAOTest > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.945 > sec > Running org.ovirt.engine.core.dao.RepoFileMetaDataDAOTest > Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 5.622 sec > Running org.ovirt.engine.core.dao.VmPoolDAOTest > Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 6.066 sec > Running org.ovirt.engine.core.dao.RoleDAOTest > Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.704 sec > Running > org.ovirt.engine.core.dao.StorageServerConnectionLunMapDAOTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.002 > sec > Running org.ovirt.engine.core.dao.VdcOptionDAOTest > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.233 > sec > Running org.ovirt.engine.core.dao.DbUserDAOTest > Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 4.518 sec > Running org.ovirt.engine.core.dao.StoragePoolIsoMapDAOTest > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.322 > sec > Running org.ovirt.engine.core.dao.AdGroupDAOTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.376 > sec > Running org.ovirt.engine.core.dao.QuotaDAOTest > Tests run: 35, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 3.789 sec > > Results : > > Tests in error: > testReplaceBrick(org.ovirt.engine.core.dao.gluster.GlusterBrickDaoTest): > Required input parameter 'v_new_brick_dir' is missing > > Tests run: 755, Failures: 0, Errors: 1, Skipped: 2 > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 3:59.609s > [INFO] Finished at: Tue Jun 12 03:44:25 EDT 2012 > [INFO] Final Memory: 10M/490M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.10:test > (default-test) on project dal: There are test failures. > [ERROR] > [ERROR] Please refer to > /home/jenkins/workspace/ovirt_engine_dao_unit_tests/backend/manager/modules/dal/target/surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with > the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug > logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > Build step 'Invoke top-level Maven targets' marked build as failure > Recording test results > Email was triggered for: Failure > Sending email for trigger: Failure > >

2 1

Re: [Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup
by Ayal Baron 12 Jun '12

12 Jun '12

> -------- Original Message -------- > Subject: [Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup > Date: Mon, 21 May 2012 06:34:32 -0400 (EDT) > From: Einav Cohen <ecohen(a)redhat.com> > To: Ayal Baron <abaron(a)redhat.com>, Eldan Hildesheim > <ehildesh(a)redhat.com>, Eldan Hildesheim <info(a)eldanet.com>, > Miki Kenneth <mkenneth(a)redhat.com>, Andrew Cathrow > <acathrow(a)redhat.com>, Simon Grinberg <sgrinber(a)redhat.com>, > Alexey Chub <achub(a)redhat.com> > CC: engine-devel(a)ovirt.org > > Please review the mock-up on the feature page: > http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience Sorry, I just saw this. The advanced features should be in an advanced tab (not easily accessible) in general I'd like to discourage users from changing these params. not sure what mount options is as it is not supported for NFS. > > Comments are welcome. > > ---- > Thanks, > Einav > _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel >

4 4

[Engine-devel] RESTAPI: what is the purpose for /api/disks collection
by Michael Pasternak 11 Jun '12

11 Jun '12

IIUC originally this collection was suppose to keep all disks that can be shared between different vms and/or available to be attached to certain vm. At the moment this collection contains all disks in system while engine does not provide any search capabilities for it, in my view it not really useful, till we add search capabilities for being able: 1. locate <shareable>true</shareable> disks 2. distinguish between <shareable>true|false</shareable> and <active>true|false</active> disks 3. maybe even worth taking <active>false</active>&&<shareable>false</shareable> out of this collection and place them under api/clusters/xxx/disks (or under DC). this way /api/disks will only have disks that can be shared. your thoughts? -- Michael Pasternak RedHat, ENG-Virtualization R&D

5 11

[Engine-devel] live migration and different technologies
by Itamar Heim 11 Jun '12

11 Jun '12

Hi Daniel, on the quantum-ovirt call today the question of live migration between multiple technologies was raised. iirc, you implemented the abstraction in libvirt between what the guest sees and the actual host networking implementation for live migration. can you please share if there are any considerations around live migrations across different network implementations (bridge, sr-iov, ovs, qbg, openflow, etc.) thanks, Itamar

3 4

[Engine-devel] Does RHEVM/Ovirt API violates the stateless requriement of REST?
by Jaroslav Henner 11 Jun '12

11 Jun '12

Hi. I think the fact that when updating (PUT), we may send only the updated xml elements violates following. http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm ------8<------8<------8<------8<------ Figure 5-2: The client-server style 5.1.3 Stateless We next add a constraint to the client-server interaction: communication must be stateless in nature, as in the client-stateless-server (CSS) style of Section 3.4.3 (Figure 5-3), such that each request from client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server. Session state is therefore kept entirely on the client. ------8<------8<------8<------8<------ Am I right? If so, this is quite huge violation. Much much bigger than some state of SESSION_ID/TOKEN. Would caches/proxies work well with current design? Jaroslav Henner.

2 1

[Engine-devel] Testing queries
by Allon Mureinik 11 Jun '12

11 Jun '12

Hi guys, following some questions from last week regarding writing unit-tests for query objects, I whipped up this quick wiki page: http://ovirt.org/wiki/Testing_Queries Enjoy, Allon

1 0

[Engine-devel] Do we need genericApi project?
by Michael Kublin 10 Jun '12

10 Jun '12

Hi, I found that we have a ovirt-engine/frontend/api/genericapi project, which is for my opinion is not at use any more. If there are any reason that we want to keep it , maybe someone using it and I missed these? Thanks Michael

5 6

[Engine-devel] [ovirt-engine-sdk] Simplify the process of the RSDL code generation
by ShaoHe Feng 10 Jun '12

10 Jun '12

This is a multi-part message in MIME format. --------------060000080308030607050901 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, Now I'm using the code generation suites of ovirt-engine-sdk, I find it is very troublesome. IMO, we can simplify the process. And I want to engaged in it. there are two tools parse the api.xsd and generate the params.py code. They are generateds_gui.py and generateDS.py. but there still some code can not be generate by these tools. now we should add these codes manually. the not NOT_GENERATED codes are as follow in the current params.py code: 1. import python module 2. a new attribute of GeneratedsSuper class 3. modify the get_root_tag function. 4. modify the parseString function to shut up the stdout. 5. _rootClassMap 6 . _elementToClassMap 7. findRootClass And I have two ideas about the code generation. For we should not modify the generateDS.py tools. But we can improve it. I think the 1, 2, 3, 7, can be hard-code, and 4, 5 and 6 can be configured. So I want to add an configure file to tell how to add the extra code that are not generated by generateDS.py tools. And new python program, as extension of generateDS.py to read the configure file and generate these codes. Or without the configure file, just make the new python program that supports an interactive commands. --------------060000080308030607050901 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi all, Now I'm using the code generation suites of ovirt-engine-sdk, I find it is very troublesome. IMO,  we can simplify the process. And I want to engaged in it. there are two tools parse the api.xsd and generate the params.py code.  They are generateds_gui.py and generateDS.py. but there still some code can not be generate by these tools. now we should add these codes manually. the not NOT_GENERATED codes are as follow in the current  params.py code: 1.  import python module 2.  a new attribute of GeneratedsSuper class 3.  modify the get_root_tag function. 4.  modify the parseString function to shut up the stdout. 5.  _rootClassMap 6 . _elementToClassMap 7. findRootClass And I have two ideas about the code generation. For we should not modify the generateDS.py tools.  But we can improve it. I think the 1, 2, 3, 7, can be hard-code, and 4, 5 and 6 can be configured. So I want to add an configure file to tell how to add the extra code that are not generated  by generateDS.py tools. And  new python program, as extension of generateDS.py to read the configure file and generate these codes. Or without the configure file, just make the new python program that supports an interactive commands. <span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 24px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(245, 245, 245); display: inline !important; float: none; "> </body> </html> --------------060000080308030607050901--

3 12

Re: [Engine-devel] Ovirt on Fedora17
by Gianluca Cecchi 08 Jun '12

08 Jun '12

On Wed Jun 6 12:07:55 EDT 2012 Oved Ourfalli wrote: > Hey, > > You should really send such question to engine-devel, as someone might have encountered such an issue, so there might be a solution for that. > Can you also attach the vdsm.log file (in the host, under the directory /var/log/vdsm/vdsm.log). > > Thank you, > Oved > >> From: ovirt at qip.ru >> To: "Oved Ourfalli" <ovedo at redhat.com> >> Sent: Wednesday, June 6, 2012 5:55:44 PM >> Subject: Re: Re: Ovirt on Fedora17 >> >> I use rpms from >> >> http:// jenkins .ovirt.org/job/ovirt_engine_create_ rpms >> /lastSuccessfulBuild/artifact/output/*zip*/output.zip Hello, I'm going to test ovrit on F17 too (both as oVirt-engine server and oVirt node). Based on http://fedoraproject.org/wiki/Features/oVirt I supposed we don't need special repo any more and we can install ovirt-engine and dependencies form default F17 repos... Is it so? Or should I enable any particular repo as in F16? Thanks in advance Gianluca

4 7

[Engine-devel] quantum-ovirt integration meeting summary
by Livnat Peer 07 Jun '12

07 Jun '12

Hi All, This is a summary of the first quantum-oVirt integration meeting. In the meeting Garry Kotton started presenting his proposal for the integration, for more details on his proposal look in - http://www.ovirt.org/wiki/Quantum_and_oVirt We did not cover much of the wiki as some question arose: * What is the end goal of the integration? is it to replace the current network configuration implementation in oVirt by quantum or have them side by side. - we need to remember non-VM networks (like storage and migration networks) * Will oVirt use multiple quantum instances, one per technology, or will oVirt use a single quantum instance that should support multiple plug-ins (not supported in Quantum ATM) * We'll oVirt support a mix of different technologies in a DC, Cluster, host? - Can we assume homogeneous clusters for the sake of simplicity (in a single cluster we'll support either open Vswitch or UCSM or ..) - Logical Network is defined in the scope of a data center, that means we need to maintain layer 2 connectivity and within a cluster we need to guarantee VM live migration (does libvirt abstract it for us?) other notes - * The UUIDs that are returned by Quantum will be managed by oVirt and for a single network implemented in two different technologies in quantum oVirt will be responsible to sync the different IDs. * The integration should be as seamless as possible to the user of oVirt * support of existing VLAN in quantum should be introduces in quantum in a 3-4 weeks time-frame Comments are welcomed, I'll schedule a follow up next week. Thanks, Livnat

3 2