June 2015 - Devel - oVirt List Archives

Maintainer rights on vdsm - ovirt-3.5-gluster
by Sahina Bose 17 Nov '15

17 Nov '15

Hi! On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga(a)redhat.com) ? thanks sahina

4 11

IO Threads + 3.6 Second Alpha Release
by Roman Nikolayevich Drovalev 30 Jul '15

30 Jul '15

Ýòî ñîîáùåíèå èç íåñêîëüêèõ ÷àñòåé â ôîðìàòå MIME. --=_alternative 00459B0D43257E74_= Content-Type: text/plain; charset="US-ASCII" Hi, This functions (IO Threads) is present in 3.6 Second Alpha Release oVirt version? http://www.ovirt.org/Features/IOThreads_Support Thanks, Drovalev Roman --=_alternative 00459B0D43257E74_= Content-Type: text/html; charset="US-ASCII" Hi, This functions (IO Threads) is present in 3.6 Second Alpha Release  oVirt version? <a href=http://www.ovirt.org/Features/IOThreads_Support>http://www.ovirt.org/Features/IOThreads_Support</a> Thanks, Drovalev Roman --=_alternative 00459B0D43257E74_=--

3 3

ovirt-engine-3.5.4 branch created
by Sandro Bonazzola 30 Jun '15

30 Jun '15

Hi, just a quick note reminding that ovirt-engine 3.5.4 branch has been created today. Any further patch targeted 3.5.4 must be cherry-picked there too. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

[ANN] oVirt 3.6.0 Second Alpha Release is now available for testing
by Sandro Bonazzola 30 Jun '15

30 Jun '15

The oVirt Project is pleased to announce the availability of the Second Alpha release of oVirt 3.6 for testing, as of June 29, 2015. oVirt is an open source alternative to VMware vSphere, and provides an excellent KVM management interface for multi-node virtualization. The Second Alpha release is available now for Fedora 20, Red Hat Enterprise Linux 6.6, CentOS 6.6 (or similar) and Red Hat Enterprise Linux 7.1, CentOS 7.1 (or similar). The Second Alpha release can also be deployed on Hypervisor Hosts running Fedora 21 and Fedora 22. Experimental support for Debian 8.1 Jessie has been added too. This Second Alpha release of oVirt includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO[2] and Node ISO[3] are already available. Please note that mirrors[4] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/el7-alpha2/ovir… [3] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node/ovirt-nod… [4] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 2

ovirt-node_master_build-artifacts-el7-x86_64 artifacts without git hashes
by Sandro Bonazzola 30 Jun '15

30 Jun '15

Hi, looking at http://jenkins.ovirt.org/job/ovirt-node_master_build-artifacts-el7-x86_64/1… I see artifacts are built without git hash. Please fix the job in order to have git hash in the rpm NVR as all other rpms have. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Upgrade to wildfly problem
by Alexander Wels 30 Jun '15

30 Jun '15

Hi, I followed the upgrade to wildfly steps here [1]. And everything worked as expected. I was able to compile/run/update database without issues. However now when I start the engine, everything appears to work but I am getting the following stack trace over and over and over again in my engine log. 2015-06-29 11:47:44,240 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-39) [] Failed to refresh VDS , vds = 'host1' : '932f05b4-e3b0-4e9a-ab99-77ff749138b3', error = 'No enum constant org.ovirt.engine.core.common.businessentities.network.NetworkBootProtocol.1', continuing. 2015-06-29 11:47:44,241 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-39) [] Exception: java.lang.IllegalArgumentException: No enum constant org.ovirt.engine.core.common.businessentities.network.NetworkBootProtocol.1 at java.lang.Enum.valueOf(Enum.java:236) [rt.jar:1.7.0_79] at org.ovirt.engine.core.common.businessentities.network.NetworkBootProtocol.valueOf(NetworkBootProtocol.java:6) [common.jar:] at org.ovirt.engine.core.dao.network.NetworkAttachmentDaoDbFacadeImpl$NetworkAttachmentRowMapper.mapRow(NetworkAttachmentDaoDbFacadeImpl.java:96) [dal.jar:] at org.ovirt.engine.core.dao.network.NetworkAttachmentDaoDbFacadeImpl$NetworkAttachmentRowMapper.mapRow(NetworkAttachmentDaoDbFacadeImpl.java:79) [dal.jar:] at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:92) [spring-jdbc.jar:3.1.1.RELEASE] at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:1) [spring-jdbc.jar:3.1.1.RELEASE] at org.springframework.jdbc.core.JdbcTemplate$1.doInPreparedStatement(JdbcTemplate.java:649) [spring-jdbc.jar:3.1.1.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:587) [spring-jdbc.jar:3.1.1.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:637) [spring-jdbc.jar:3.1.1.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:666) [spring-jdbc.jar:3.1.1.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:706) [spring-jdbc.jar:3.1.1.RELEASE] at org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.executeCallInternal(PostgresDbEngineDialect.java:154) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.doExecute(PostgresDbEngineDialect.java:120) [dal.jar:] at org.springframework.jdbc.core.simple.SimpleJdbcCall.execute(SimpleJdbcCall.java:181) [spring-jdbc.jar:3.1.1.RELEASE] at org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:147) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeReadList(SimpleJdbcCallsHandler.java:109) [dal.jar:] at org.ovirt.engine.core.dao.network.NetworkAttachmentDaoDbFacadeImpl.getAllForHost(NetworkAttachmentDaoDbFacadeImpl.java:40) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.HostNetworkAttachmentsPersister.persistNetworkAttachments(HostNetworkAttachmentsPersister.java:69) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.HostNetworkTopologyPersisterImpl.persistTopology(HostNetworkTopologyPersisterImpl.java:280) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.HostNetworkTopologyPersisterImpl.persistAndEnforceNetworkCompliance(HostNetworkTopologyPersisterImpl.java:85) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.HostNetworkTopologyPersisterImpl.persistAndEnforceNetworkCompliance(HostNetworkTopologyPersisterImpl.java:141) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:666) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.HostMonitoring.beforeFirstRefreshTreatment(HostMonitoring.java:706) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:128) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.HostMonitoring.refresh(HostMonitoring.java:84) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:215) [vdsbroker.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79] at org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:81) [scheduler.jar:] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:52) [scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz.jar:] After some debugging it appears that the query from the database returns "1" as the value (which is correct as that is the value in the database). But then the NetworkBootProtocol.forValue fails due to the possible values being "NONE", "DHCP", "STATIC". Looking at the stored procedure there doesn't seem to be any translation between 1 and DHCP, so it makes sense for the failure. I compared the stored procedure to a clean new database and they are identical, so I am assuming my database is fine in that regard. If I modify the code to use NetworkBootProtocol.forValue instead of valueOf it works fine, but the valueOf code has been in there for a long time so if that was broken it would have been noticed a long time ago. I am out of thoughts, can anyone help me figure out what is going on? Thanks, Alexander [1] http://lists.ovirt.org/pipermail/devel/2015-June/010832.html

3 3

Re: [ovirt-devel] [TICKET] failing gluster tests -- RefreshGlusterVolumeDetailsCommandTest
by Doron Fediuck 30 Jun '15

30 Jun '15

Adding rhev-gluster. Vijay / Sahina can you please review? On Jun 26, 2015 12:12, Eyal Edri <eedri(a)redhat.com> wrote: > > > > ----- Original Message ----- > > From: "Sandro Bonazzola" <sbonazzo(a)redhat.com> > > To: "Doron Fediuck" <dfediuck(a)redhat.com>, "Greg Sheremeta" <gshereme(a)redhat.com>, "infra" <infra(a)ovirt.org>, > > devel(a)ovirt.org, "Sahina Bose" <sabose(a)redhat.com> > > Sent: Friday, June 26, 2015 10:55:51 AM > > Subject: Re: [ovirt-devel] [TICKET] failing gluster tests -- RefreshGlusterVolumeDetailsCommandTest > > > > Il 25/06/2015 17:53, Doron Fediuck ha scritto: > > > Sahina, any idea? > > > > > > On 25/06/15 18:06, Greg Sheremeta wrote: > > >> These tests appear to be randomly failing in Jenkins. Was this a > > >> memory issue? Pretty odd error -- "Could not initialize class" -- > > >> never seen that one before. > > >> > > >> It worked on a dependent patch's build, and I didn't touch any > > >> gluster stuff. > > >> > > >> http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_gerrit/40725/co… > > >> > > >> Thanks, > > >> Greg > > >> > > >> > > >> 15:56:32 Results : > > >> 15:56:32 > > >> 15:56:32 Tests in error: > > >> 15:56:32 > > >> org.ovirt.engine.core.bll.gluster.RefreshGlusterVolumeDetailsCommandTest > > >> 15:56:32 > > >> testRefreshLightWeight(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): > > >> Could not initialize class > > >> org.ovirt.engine.core.bll.gluster.GlusterSyncJob > > >> 15:56:32 > > >> testRefreshHeavyWeightFor31(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): > > >> Could not initialize class > > >> org.ovirt.engine.core.bll.gluster.GlusterSyncJob > > >> 15:56:32 > > >> testRefreshHeavyWeightFor32(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): > > >> Could not initialize class > > >> org.ovirt.engine.core.bll.gluster.GlusterSyncJob > > >> 15:56:32 > > >> testRefreshLightWeightFor33(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): > > >> Could not initialize class > > >> org.ovirt.engine.core.bll.gluster.GlusterSyncJob > > >> 15:56:32 > > >> 15:56:32 Tests run: 2341, Failures: 0, Errors: 5, Skipped: 6 > > >> 15:56:32 > > > > Just sent an email about the same error. It's reproducible near to 100% > > please address as soon as possible. > > > > this was the latest gluster patch related: https://gerrit.ovirt.org/#/c/42863/ > might worth to revert until fixed. > > > > > > > >> > > >> Greg Sheremeta > > >> Red Hat, Inc. > > >> Sr. Software Engineer, RHEV > > >> Cell: 919-807-1086 > > >> gshereme(a)redhat.com > > >> _______________________________________________ > > >> Devel mailing list > > >> Devel(a)ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/devel > > >> > > > > > > _______________________________________________ > > > Devel mailing list > > > Devel(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > -- > > Sandro Bonazzola > > Better technology. Faster innovation. Powered by community collaboration. > > See how it works at redhat.com > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > > -- > Eyal Edri > Supervisor, RHEV CI > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 4

Fwd: Orphaning jasperreports
by Yedidyah Bar David 30 Jun '15

30 Jun '15

It seems like the engine depends on jasperreports (not jasperreports-server, needed by ovirt-reports - this one we package in ovirt repos). Not sure the following is the only path: ovirt-engine requires openstack-java-resteasy-connector >= 3.1.1 openstack-java-resteasy-connector requires mvn(org.jboss.resteasy:resteasy-jaxrs) mvn(org.jboss.resteasy:resteasy-jaxrs) is provided by resteasy resteasy requires mvn(org.springframework:spring-webmvc) mvn(org.springframework:spring-webmvc) is provided by springframework-webmvc springframework-webmvc requires mvn(net.sf.jasperreports:jasperreports) mvn(net.sf.jasperreports:jasperreports) is provided by jasperreports FYI. Best, -- Didi ----- Forwarded Message ----- From: "Sandro Bonazzola" <sbonazzo(a)redhat.com> To: "Shirly Radco" <sradco(a)redhat.com>, "Yedidyah Bar David" <didi(a)redhat.com>, "Yaniv Dary" <ydary(a)redhat.com> Sent: Monday, June 22, 2015 4:16:26 PM Subject: Fwd: Orphaning jasperreports FYI -------- Messaggio Inoltrato -------- Oggetto: Orphaning jasperreports Data: Mon, 22 Jun 2015 14:56:55 +0200 Mittente: gil <puntogil(a)libero.it> Rispondi-a: Development discussions related to Fedora <devel(a)lists.fedoraproject.org> A: Fedora Java Development List <java-devel(a)lists.fedoraproject.org>, Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, bigdata(a)lists.fedoraproject.org HI I have intention to orphaning/retire jasperreports [1] , because it fails build [2] with new batik (1.8) and newer release use non free itext 5.x library. [1] https://admin.fedoraproject.org/pkgdb/package/jasperreports/ [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=10098415 -- devel mailing list devel(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

2 1

fyi - outage in jenkins.ovirt.org
by Eyal Edri 29 Jun '15

29 Jun '15

fyi, there is currently an outage with jenkins.ovirt.org, seems related to an out of memory issue. the infra team is investigating and will report when the issue is resolved. you might experience some errors or infra issues with jenkins jobs running on patches, if there is something urgent that can't wait for the fix, please let us know. we hope the issue can be resolved within the next hour. oVirt infra.

2 2

Gluster patches on Alpha-1
by Christopher Pereira 29 Jun '15

29 Jun '15

This is a multi-part message in MIME format. --------------030000060002050801070903 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sandro, Can you please confirm this patches where released in alpha-1? https://gerrit.ovirt.org/#/c/40239/ https://gerrit.ovirt.org/#/c/40240/ I just tested alpha-1 and vdsmd restart is still killing glusterd and all VMs because it is running glusterd inside vdsmd's cgroup. Can we please include them in alpha-2? It's too dangerous to kill the storage because it corrupts VMs, specially Windows ones. Thanks. --------------030000060002050801070903 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Sandro, Can you please confirm this patches where released in alpha-1? <blockquote><a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/40239/">https://gerrit.ovirt.org/#/c/40239/</a> <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/40240/">https://gerrit.ovirt.org/#/c/40240/</a> </blockquote> I just tested alpha-1 and vdsmd restart is still killing glusterd and all VMs because it is running glusterd inside vdsmd's cgroup. Can we please include them in alpha-2? It's too dangerous to kill the storage because it corrupts VMs, specially Windows ones. Thanks. </body> </html> --------------030000060002050801070903--

2 1

Merge patch "qemuimg: add support for convert progress"
by Christopher Pereira 28 Jun '15

28 Jun '15

qemu-img operations can take very long and there is currently no way to see their progress. It would be nice to include this patch to display the progress of a qemu-img operation (uploaded in November): https://gerrit.ovirt.org/#/c/33910/ Canceling the qemu-img task from Engine is also something that should be addressed at some point. 'copyImage' tasks are displayed via vdsClient. Is there any particular reason why a "Cancel" button was never added to the Engine's Task list?

2 1

engine-setup broken in master?
by Omer Frenkel 28 Jun '15

28 Jun '15

Hi, on latest master, engine-setup fails for me with: [ ERROR ] Failed to execute stage 'Setup validation': Failed checking Engine database: [u''] from the setup log: 2015-06-25 10:27:51 DEBUG otopi.plugins.ovirt_**FILTERED**_setup.ovirt_**FILTERED**.upgrade.dbvalidations plugin.execute:940 execute-output: ['/home/ofrenkel/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/dbu tils/validatedb.sh', '--user=**FILTERED**', '--host=localhost', '--port=5432', '--database=**FILTERED**', '--log=/home/ofrenkel/ovirt-**FILTERED**/var/log/ovirt-**FILTERED**/setup/ovirt-**FILTERED**-setup-201506 25102702-nwwazb.log'] stderr: ERROR: function fn_db_validate_fks(boolean, boolean) does not exist LINE 3: from fn_db_validate_fks(false, 0 != 0) ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2015-06-25 10:27:51 DEBUG otopi.context context._executeMethod:155 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 145, in _executeMethod method['method']() File "/home/ofrenkel/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/upgrade/dbvalidations.py", line 128, in _validation violations, issues_found = self._checkDb() File "/home/ofrenkel/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/upgrade/dbvalidations.py", line 91, in _checkDb output=stdout, RuntimeError: Failed checking Engine database: [u''] 2015-06-25 10:27:51 ERROR otopi.context context._executeMethod:164 Failed to execute stage 'Setup validation': Failed checking Engine database: [u''] ---- looks like lately this function (fn_db_validate_fks) was moved, might be related? ( https://gerrit.ovirt.org/#/c/42655/ ) i even tried to completely remove my ~/ovirt-engine/ folder and create from scratch anyone else experienced this? Thanks, Omer.

7 10

[TICKET] failing gluster tests -- RefreshGlusterVolumeDetailsCommandTest
by Greg Sheremeta 26 Jun '15

26 Jun '15

These tests appear to be randomly failing in Jenkins. Was this a memory issue? Pretty odd error -- "Could not initialize class" -- never seen that one before. It worked on a dependent patch's build, and I didn't touch any gluster stuff. http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_gerrit/40725/co… Thanks, Greg 15:56:32 Results : 15:56:32 15:56:32 Tests in error: 15:56:32 org.ovirt.engine.core.bll.gluster.RefreshGlusterVolumeDetailsCommandTest 15:56:32 testRefreshLightWeight(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob 15:56:32 testRefreshHeavyWeightFor31(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob 15:56:32 testRefreshHeavyWeightFor32(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob 15:56:32 testRefreshLightWeightFor33(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob 15:56:32 15:56:32 Tests run: 2341, Failures: 0, Errors: 5, Skipped: 6 15:56:32 Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

4 3

Re: [ovirt-devel] vdsm_master_unit-tests_merged stuck again on JsonRpcServerTests
by Piotr Kliczewski 26 Jun '15

26 Jun '15

----_com.android.email_307787486177500 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 CiAgICAKVGhpcyBlcnJvciBpcyB0aHJvd24gd2hlbiB0aGUgdGVzdCB0aW1lb3V0cy4gSSByZWR1 Y2VkIHRpbWVvdXQgdG8gYmUgc3VyZSB0aGF0IHRoZXJlIGlzIG5vIGlzc3VlIHdpdGggdGltZW91 dHMuIFdlIHNhdyB0ZXN0cyBiZWluZyBzdHVjay4gT25jZSB3ZSBkbyBub3Qgc2VlIGl0IGhhbmdp bmcgYWdhaW4gaSB3aWxsIHJlc3RvcmUgcHJldmlvcyB2YWx1ZS4KCgpUaGFua3MsUGlvdHIKCi0t LS0tLS0tIE9yeWdpbmFsbmEgd2lhZG9tb8WbxIcgLS0tLS0tLS0KT2Q6IERhbiBLZW5pZ3NiZXJn IDxkYW5rZW5AcmVkaGF0LmNvbT4gCkRhdGE6IDI1LjA2LjIwMTUgIDIyOjMzICAoR01UKzAxOjAw KSAKRG86IFBpb3RyIEtsaWN6ZXdza2kgPHBpb3RyLmtsaWN6ZXdza2lAZ21haWwuY29tPiAKRFc6 IFBpb3RyIEtsaWN6ZXdza2kgPHBrbGljemV3QHJlZGhhdC5jb20+LCBpbmZyYSA8aW5mcmFAb3Zp cnQub3JnPiwgZGV2ZWxAb3ZpcnQub3JnIApUZW1hdDogUmU6IFtvdmlydC1kZXZlbF0gdmRzbV9t YXN0ZXJfdW5pdC10ZXN0c19tZXJnZWQgc3R1Y2sgYWdhaW4gb24gSnNvblJwY1NlcnZlclRlc3Rz IAoKCkkgc2VlIHRoYXQgeW91IGhhdmUgcmUtZW5hYmxlZCB0aGUgdGVzdHMgLSB0aGFua3MuCgpQ bGVhc2Ugbm90ZSB0aGF0IG5vdyBJIHNlZSBhIHJhbmRvbQoKMjA6MjU6NDkgPT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQoyMDoyNTo0OSBFUlJPUjogdGVzdE1ldGhvZFJldHVybnNOdWxsQW5kU2VydmVyUmV0dXJuc1Ry dWUoa3c9RmFsc2UpIChqc29uUnBjVGVzdHMuSnNvblJwY1NlcnZlclRlc3RzKQoyMDoyNTo0OSAt LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tCjIwOjI1OjQ5IFRyYWNlYmFjayAobW9zdCByZWNlbnQgY2FsbCBsYXN0KToK MjA6MjU6NDnCoMKgIEZpbGUgIi90bXAvcnVuL3Zkc20vdGVzdHMvdGVzdGxpYi5weSIsIGxpbmUg NjQsIGluIHdyYXBwZXIKMjA6MjU6NDnCoMKgwqDCoCByZXR1cm4gZihzZWxmLCAqYXJncykKMjA6 MjU6NDnCoMKgIEZpbGUgIi90bXAvcnVuL3Zkc20vdGVzdHMvbW9ua2V5cGF0Y2gucHkiLCBsaW5l IDEzMywgaW4gd3JhcHBlcgoyMDoyNTo0OcKgwqDCoMKgIHJldHVybiBmKCphcmdzLCAqKmt3KQoy MDoyNTo0OcKgwqAgRmlsZSAiL3RtcC9ydW4vdmRzbS90ZXN0cy9qc29uUnBjVGVzdHMucHkiLCBs aW5lIDE4NiwgaW4gdGVzdE1ldGhvZFJldHVybnNOdWxsQW5kU2VydmVyUmV0dXJuc1RydWUKMjA6 MjU6NDnCoMKgwqDCoCBDQUxMX0lEKQoyMDoyNTo0OcKgwqAgRmlsZSAiL3RtcC9ydW4vdmRzbS90 ZXN0cy9qc29uUnBjVGVzdHMucHkiLCBsaW5lIDg5LCBpbiBfY2FsbFRpbWVvdXQKMjA6MjU6NDnC oMKgwqDCoCByYWlzZSBKc29uUnBjTm9SZXNwb25zZUVycm9yKG1ldGhvZE5hbWUpCjIwOjI1OjQ5 IEpzb25ScGNOb1Jlc3BvbnNlRXJyb3I6IFstMzI2MDVdIE5vIHJlc3BvbnNlIGZvciBKU09OLVJQ QyBwaW5nIHJlcXVlc3QuCgppbiBodHRwOi8vamVua2lucy5vdmlydC5vcmcvam9iL3Zkc21fbWFz dGVyX3VuaXQtdGVzdHNfY3JlYXRlZC80MDk2L2NvbnNvbGUKCmNhbiB5b3UgdGFrZSBhIGxvb2s/ Cg== ----_com.android.email_307787486177500 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT4KICAgIAo8ZGl2PlRoaXMgZXJyb3Ig aXMgdGhyb3duIHdoZW4gdGhlIHRlc3QgdGltZW91dHMuIEkgcmVkdWNlZCB0aW1lb3V0IHRvIGJl IHN1cmUgdGhhdCB0aGVyZSBpcyBubyBpc3N1ZSB3aXRoIHRpbWVvdXRzLiBXZSBzYXcgdGVzdHMg YmVpbmcgc3R1Y2suIE9uY2Ugd2UgZG8gbm90IHNlZSBpdCBoYW5naW5nIGFnYWluIGkgd2lsbCBy ZXN0b3JlIHByZXZpb3MgdmFsdWUuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+ PGRpdj48YnI+PC9kaXY+PGRpdiBpZD0iY29tcG9zZXJfc2lnbmF0dXJlIj48ZGl2IHN0eWxlPSJm b250LXNpemU6OXB4Ij5UaGFua3MsPC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOjlweCI+UGlv dHI8L2Rpdj48L2Rpdj48YnI+PGJyPjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMDAlO3RleHQtYWxp Z246bGVmdDtjb2xvcjojMDAwMDAwIj4tLS0tLS0tLSBPcnlnaW5hbG5hIHdpYWRvbW/Fm8SHIC0t LS0tLS0tPGJyPk9kOiBEYW4gS2VuaWdzYmVyZyAmbHQ7ZGFua2VuQHJlZGhhdC5jb20mZ3Q7IDxi cj5EYXRhOiAyNS4wNi4yMDE1ICAyMjozMyAgKEdNVCswMTowMCkgPGJyPkRvOiBQaW90ciBLbGlj emV3c2tpICZsdDtwaW90ci5rbGljemV3c2tpQGdtYWlsLmNvbSZndDsgPGJyPkRXOiBQaW90ciBL bGljemV3c2tpICZsdDtwa2xpY3pld0ByZWRoYXQuY29tJmd0OywgaW5mcmEgJmx0O2luZnJhQG92 aXJ0Lm9yZyZndDssIGRldmVsQG92aXJ0Lm9yZyA8YnI+VGVtYXQ6IFJlOiBbb3ZpcnQtZGV2ZWxd IHZkc21fbWFzdGVyX3VuaXQtdGVzdHNfbWVyZ2VkIHN0dWNrIGFnYWluIG9uIEpzb25ScGNTZXJ2 ZXJUZXN0cyA8YnI+PGJyPjwvZGl2Pjxicj5JIHNlZSB0aGF0IHlvdSBoYXZlIHJlLWVuYWJsZWQg dGhlIHRlc3RzIC0gdGhhbmtzLjxicj48YnI+UGxlYXNlIG5vdGUgdGhhdCBub3cgSSBzZWUgYSBy YW5kb208YnI+PGJyPjIwOjI1OjQ5ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08YnI+MjA6MjU6NDkgRVJST1I6IHRl c3RNZXRob2RSZXR1cm5zTnVsbEFuZFNlcnZlclJldHVybnNUcnVlKGt3PUZhbHNlKSAoanNvblJw Y1Rlc3RzLkpzb25ScGNTZXJ2ZXJUZXN0cyk8YnI+MjA6MjU6NDkgLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4y MDoyNTo0OSBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFzdCk6PGJyPjIwOjI1OjQ5Jm5i c3A7Jm5ic3A7IEZpbGUgIi90bXAvcnVuL3Zkc20vdGVzdHMvdGVzdGxpYi5weSIsIGxpbmUgNjQs IGluIHdyYXBwZXI8YnI+MjA6MjU6NDkmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgcmV0dXJuIGYo c2VsZiwgKmFyZ3MpPGJyPjIwOjI1OjQ5Jm5ic3A7Jm5ic3A7IEZpbGUgIi90bXAvcnVuL3Zkc20v dGVzdHMvbW9ua2V5cGF0Y2gucHkiLCBsaW5lIDEzMywgaW4gd3JhcHBlcjxicj4yMDoyNTo0OSZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyByZXR1cm4gZigqYXJncywgKiprdyk8YnI+MjA6MjU6NDkm bmJzcDsmbmJzcDsgRmlsZSAiL3RtcC9ydW4vdmRzbS90ZXN0cy9qc29uUnBjVGVzdHMucHkiLCBs aW5lIDE4NiwgaW4gdGVzdE1ldGhvZFJldHVybnNOdWxsQW5kU2VydmVyUmV0dXJuc1RydWU8YnI+ MjA6MjU6NDkmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgQ0FMTF9JRCk8YnI+MjA6MjU6NDkmbmJz cDsmbmJzcDsgRmlsZSAiL3RtcC9ydW4vdmRzbS90ZXN0cy9qc29uUnBjVGVzdHMucHkiLCBsaW5l IDg5LCBpbiBfY2FsbFRpbWVvdXQ8YnI+MjA6MjU6NDkmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg cmFpc2UgSnNvblJwY05vUmVzcG9uc2VFcnJvcihtZXRob2ROYW1lKTxicj4yMDoyNTo0OSBKc29u UnBjTm9SZXNwb25zZUVycm9yOiBbLTMyNjA1XSBObyByZXNwb25zZSBmb3IgSlNPTi1SUEMgcGlu ZyByZXF1ZXN0Ljxicj48YnI+aW4gaHR0cDovL2plbmtpbnMub3ZpcnQub3JnL2pvYi92ZHNtX21h c3Rlcl91bml0LXRlc3RzX2NyZWF0ZWQvNDA5Ni9jb25zb2xlPGJyPjxicj5jYW4geW91IHRha2Ug YSBsb29rPzxicj48L2JvZHk+PC9odG1sPg== ----_com.android.email_307787486177500--

3 2

[URGENT] ovirt-engine failing to build due to "Could not initialize class" error
by Sandro Bonazzola 26 Jun '15

26 Jun '15

Tests in error: org.ovirt.engine.core.bll.gluster.RefreshGlusterVolumeDetailsCommandTest testRefreshLightWeight(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob testRefreshHeavyWeightFor31(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob testRefreshHeavyWeightFor32(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob testRefreshLightWeightFor33(org.ovirt.engine.core.bll.gluster.GlusterSyncJobTest): Could not initialize class org.ovirt.engine.core.bll.gluster.GlusterSyncJob Looks like it's quite reproducible with current master. Please fix it ASAP -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

ovirt-engine failing to build on F22 mock chroot (org.apache.maven.plugins:maven-ear-plugin:2.8)
by Sandro Bonazzola 26 Jun '15

26 Jun '15

Hi, while ovirt-engine is currently building fine in mock chroots for el6[1] and el7[2] we have not a successfull build on F22[3] yet. The error is always the same[4]: [INFO] Building oVirt Server EAR 3.6.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] Using transporter WagonTransporter with priority -1.0 for http://artifactory.ovirt.org:8081/artifactory/ovirt-mirror [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://artifactory.ovirt.org:8081/artifactory/ovirt-mirror Downloading: http://artifactory.ovirt.org:8081/artifactory/ovirt-mirror/org/apache/maven… Jun 25, 2015 2:15:43 PM org.apache.http.impl.execchain.RetryExec execute INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://artifactory.ovirt.org:8081: The target server failed to respond Jun 25, 2015 2:15:43 PM org.apache.http.impl.execchain.RetryExec execute INFO: Retrying request to {}->http://artifactory.ovirt.org:8081 Jun 25, 2015 2:15:43 PM org.apache.http.impl.execchain.RetryExec execute INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://artifactory.ovirt.org:8081: The target server failed to respond Jun 25, 2015 2:15:43 PM org.apache.http.impl.execchain.RetryExec execute INFO: Retrying request to {}->http://artifactory.ovirt.org:8081 Jun 25, 2015 2:15:43 PM org.apache.http.impl.execchain.RetryExec execute INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://artifactory.ovirt.org:8081: The target server failed to respond Jun 25, 2015 2:15:43 PM org.apache.http.impl.execchain.RetryExec execute INFO: Retrying request to {}->http://artifactory.ovirt.org:8081 [DEBUG] Writing tracking file /builddir/.m2/repository/org/apache/maven/plugins/maven-ear-plugin/2.8/maven-ear-plugin-2.8.pom.lastUpdated [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] ovirt-root ......................................... SUCCESS [ 11.298 s] [INFO] oVirt Build Tools root ............................. SUCCESS [ 0.037 s] [INFO] oVirt checkstyle ................................... SUCCESS [ 43.241 s] [INFO] oVirt JBoss Modules Maven Plugin ................... SUCCESS [01:02 min] [INFO] oVirt Checkstyle Checks ............................ SUCCESS [ 5.961 s] [INFO] Extensions API root ................................ SUCCESS [ 9.771 s] [INFO] ovirt-engine-extensions-api ........................ SUCCESS [ 48.433 s] [INFO] oVirt Modules - backend ............................ SUCCESS [ 0.006 s] [INFO] oVirt Manager ...................................... SUCCESS [ 0.004 s] [INFO] oVirt Engine dependencies .......................... SUCCESS [ 0.004 s] [INFO] oVirt Engine common dependencies ................... SUCCESS [ 46.326 s] [INFO] oVirt Engine tools dependencies .................... SUCCESS [ 0.924 s] [INFO] oVirt Modules - manager ............................ SUCCESS [ 2.952 s] [INFO] Universal utilities ................................ SUCCESS [ 14.372 s] [INFO] Extensions manager ................................. SUCCESS [ 4.444 s] [INFO] CSharp Compatibility ............................... SUCCESS [ 5.638 s] [INFO] Common Code ........................................ SUCCESS [ 29.187 s] [INFO] Common utilities ................................... SUCCESS [ 47.238 s] [INFO] Data Access Layer .................................. SUCCESS [ 20.566 s] [INFO] engine scheduler bean .............................. SUCCESS [ 2.681 s] [INFO] Vds broker ......................................... SUCCESS [ 15.109 s] [INFO] Backend Authentication, Authorization and Accounting SUCCESS [ 3.786 s] [INFO] builtin-extensions ................................. SUCCESS [ 3.970 s] [INFO] Search Backend ..................................... SUCCESS [ 5.493 s] [INFO] Branding package ................................... SUCCESS [ 3.688 s] [INFO] Backend Logic @Service bean ........................ SUCCESS [01:02 min] [INFO] oVirt RESTful API Backend Integration .............. SUCCESS [ 5.883 s] [INFO] oVirt RESTful API interface ........................ SUCCESS [ 0.130 s] [INFO] oVirt Engine API Definition ........................ SUCCESS [ 30.769 s] [INFO] oVirt Engine API Commom Parent POM ................. SUCCESS [ 0.122 s] [INFO] oVirt Engine API Common JAX-RS ..................... SUCCESS [ 6.839 s] [INFO] oVirt RESTful API Backend Integration Type Mappers . SUCCESS [ 11.986 s] [INFO] oVirt RESTful API Backend Integration JAX-RS Resources SUCCESS [ 58.359 s] [INFO] oVirt RESTful API Backend Integration Webapp ....... SUCCESS [ 4.075 s] [INFO] Custom Logger Using Extensions ..................... SUCCESS [ 1.443 s] [INFO] oVirt Engine Web Root .............................. SUCCESS [ 0.465 s] [INFO] ovirt-engine services .............................. SUCCESS [ 1.657 s] [INFO] oVirt Engine Web Docs .............................. SUCCESS [ 2.373 s] [INFO] ovirt-engine welcome ............................... SUCCESS [ 2.379 s] [INFO] oVirt Engine Tools ................................. SUCCESS [ 5.372 s] [INFO] oVirt Engine extensions tool ....................... SUCCESS [ 1.484 s] [INFO] oVirt Modules :: Frontend .......................... SUCCESS [ 0.015 s] [INFO] oVirt Modules :: Webadmin .......................... SUCCESS [ 0.011 s] [INFO] oVirt Modules - ui ................................. SUCCESS [ 0.011 s] [INFO] Extensions for GWT ................................. SUCCESS [ 12.406 s] [INFO] UI Utils Compatibility (for UICommon) .............. SUCCESS [ 24.050 s] [INFO] Frontend for GWT UI Projects ....................... SUCCESS [ 22.719 s] [INFO] UICommonWeb ........................................ SUCCESS [ 28.329 s] [INFO] oVirt GWT UI common infrastructure ................. SUCCESS [ 25.396 s] [INFO] WebAdmin ........................................... SUCCESS [ 01:48 h] [INFO] UserPortal ......................................... SUCCESS [46:24 min] [INFO] frontend-symbols ................................... SUCCESS [04:28 min] [INFO] oVirt Server EAR ................................... FAILURE [ 1.520 s] [INFO] ovirt-engine maven make ............................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:50 h [INFO] Finished at: 2015-06-25T14:15:43+00:00 [INFO] Final Memory: 534M/1300M [INFO] ------------------------------------------------------------------------ [ERROR] Plugin org.apache.maven.plugins:maven-ear-plugin:2.8 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ear-plugin:jar:2.8: Could not transfer artifact org.apache.maven.plugins:maven-ear-plugin:pom:2.8 from/to ovirt-maven-repository (http://artifactory.ovirt.org:8081/artifactory/ovirt-mirror) artifactory.ovirt.org:8081 failed to respond -> [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ear-plugin:2.8 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ear-plugin:jar:2.8 We tried dropping the mirror we currently use (artifactory.ovirt.org) and the issue still persist on maven central[5]: [INFO] Building oVirt Server EAR 3.6.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] Using transporter WagonTransporter with priority -1.0 for http://repo1.maven.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2.8… Jun 25, 2015 5:12:14 PM org.apache.http.impl.execchain.RetryExec execute INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://repo1.maven.org:80: The target server failed to respond Jun 25, 2015 5:12:14 PM org.apache.http.impl.execchain.RetryExec execute INFO: Retrying request to {}->http://repo1.maven.org:80 Jun 25, 2015 5:12:14 PM org.apache.http.impl.execchain.RetryExec execute INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://repo1.maven.org:80: The target server failed to respond Jun 25, 2015 5:12:14 PM org.apache.http.impl.execchain.RetryExec execute INFO: Retrying request to {}->http://repo1.maven.org:80 Jun 25, 2015 5:12:14 PM org.apache.http.impl.execchain.RetryExec execute INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://repo1.maven.org:80: The target server failed to respond Jun 25, 2015 5:12:14 PM org.apache.http.impl.execchain.RetryExec execute INFO: Retrying request to {}->http://repo1.maven.org:80 [DEBUG] Writing tracking file /builddir/.m2/repository/org/apache/maven/plugins/maven-ear-plugin/2.8/maven-ear-plugin-2.8.pom.lastUpdated [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] ovirt-root ......................................... SUCCESS [ 3.592 s] [INFO] oVirt Build Tools root ............................. SUCCESS [ 0.018 s] [INFO] oVirt checkstyle ................................... SUCCESS [ 11.771 s] [INFO] oVirt JBoss Modules Maven Plugin ................... SUCCESS [ 21.113 s] [INFO] oVirt Checkstyle Checks ............................ SUCCESS [ 1.923 s] [INFO] Extensions API root ................................ SUCCESS [ 2.439 s] [INFO] ovirt-engine-extensions-api ........................ SUCCESS [ 14.167 s] [INFO] oVirt Modules - backend ............................ SUCCESS [ 0.005 s] [INFO] oVirt Manager ...................................... SUCCESS [ 0.004 s] [INFO] oVirt Engine dependencies .......................... SUCCESS [ 0.003 s] [INFO] oVirt Engine common dependencies ................... SUCCESS [ 22.972 s] [INFO] oVirt Engine tools dependencies .................... SUCCESS [ 0.176 s] [INFO] oVirt Modules - manager ............................ SUCCESS [ 1.211 s] [INFO] Universal utilities ................................ SUCCESS [ 4.604 s] [INFO] Extensions manager ................................. SUCCESS [ 2.597 s] [INFO] CSharp Compatibility ............................... SUCCESS [ 3.840 s] [INFO] Common Code ........................................ SUCCESS [ 19.349 s] [INFO] Common utilities ................................... SUCCESS [ 12.360 s] [INFO] Data Access Layer .................................. SUCCESS [ 13.140 s] [INFO] engine scheduler bean .............................. SUCCESS [ 2.266 s] [INFO] Vds broker ......................................... SUCCESS [ 11.081 s] [INFO] Backend Authentication, Authorization and Accounting SUCCESS [ 3.417 s] [INFO] builtin-extensions ................................. SUCCESS [ 3.581 s] [INFO] Search Backend ..................................... SUCCESS [ 4.347 s] [INFO] Branding package ................................... SUCCESS [ 2.920 s] [INFO] Backend Logic @Service bean ........................ SUCCESS [ 33.454 s] [INFO] oVirt RESTful API Backend Integration .............. SUCCESS [ 1.095 s] [INFO] oVirt RESTful API interface ........................ SUCCESS [ 0.135 s] [INFO] oVirt Engine API Definition ........................ SUCCESS [ 16.550 s] [INFO] oVirt Engine API Commom Parent POM ................. SUCCESS [ 0.118 s] [INFO] oVirt Engine API Common JAX-RS ..................... SUCCESS [ 3.693 s] [INFO] oVirt RESTful API Backend Integration Type Mappers . SUCCESS [ 6.818 s] [INFO] oVirt RESTful API Backend Integration JAX-RS Resources SUCCESS [ 17.311 s] [INFO] oVirt RESTful API Backend Integration Webapp ....... SUCCESS [ 1.006 s] [INFO] Custom Logger Using Extensions ..................... SUCCESS [ 1.063 s] [INFO] oVirt Engine Web Root .............................. SUCCESS [ 0.172 s] [INFO] ovirt-engine services .............................. SUCCESS [ 2.136 s] [INFO] oVirt Engine Web Docs .............................. SUCCESS [ 1.256 s] [INFO] ovirt-engine welcome ............................... SUCCESS [ 2.021 s] [INFO] oVirt Engine Tools ................................. SUCCESS [ 4.333 s] [INFO] oVirt Engine extensions tool ....................... SUCCESS [ 0.944 s] [INFO] oVirt Modules :: Frontend .......................... SUCCESS [ 0.003 s] [INFO] oVirt Modules :: Webadmin .......................... SUCCESS [ 0.003 s] [INFO] oVirt Modules - ui ................................. SUCCESS [ 0.002 s] [INFO] Extensions for GWT ................................. SUCCESS [ 4.081 s] [INFO] UI Utils Compatibility (for UICommon) .............. SUCCESS [ 6.789 s] [INFO] Frontend for GWT UI Projects ....................... SUCCESS [ 14.630 s] [INFO] UICommonWeb ........................................ SUCCESS [ 24.714 s] [INFO] oVirt GWT UI common infrastructure ................. SUCCESS [ 21.495 s] [INFO] WebAdmin ........................................... SUCCESS [ 01:46 h] [INFO] UserPortal ......................................... SUCCESS [45:49 min] [INFO] frontend-symbols ................................... SUCCESS [01:24 min] [INFO] oVirt Server EAR ................................... FAILURE [ 0.531 s] [INFO] ovirt-engine maven make ............................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:39 h [INFO] Finished at: 2015-06-25T17:12:14+00:00 [INFO] Final Memory: 526M/1200M [INFO] ------------------------------------------------------------------------ [ERROR] Plugin org.apache.maven.plugins:maven-ear-plugin:2.8 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ear-plugin:jar:2.8: Could not transfer artifact org.apache.maven.plugins:maven-ear-plugin:pom:2.8 from/to central (http://repo1.maven.org/maven2) repo1.maven.org:80 failed to respond -> [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ear-plugin:2.8 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ear-plugin:jar:2.8 Any hint on how to resolve the issue? [1] http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms-el6-x86_64_mer… [2] http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms-el7-x86_64_mer… [3] http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms-fc22-x86_64_me… [4] http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms-fc22-x86_64_me… [5] http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms-fc22-x86_64_me… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

vdsm_master_unit-tests_merged stuck again on JsonRpcServerTests
by Sandro Bonazzola 25 Jun '15

25 Jun '15

http://jenkins.ovirt.org/job/vdsm_master_unit-tests_merged/326/console Last lines: JsonRpcServerTests testDoubleResponse(kw=False) OK testDoubleResponse(kw=True) OK testMethodBadParameters(kw=False) OK testMethodBadParameters(kw=True) OK job is still running on fc20-vm06.phx.ovirt.org Please investigate before killing the job. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 5

[VDSM] Live snapshot with ceph disks
by Nir Soffer 25 Jun '15

25 Jun '15

Hi all, For 3.6, we will not support live vm snapshot, but this is a must for the next release. It is trivial to create a disk snapshot in ceph (using cinder apis). The snapshot is transparent to libvirt, qmeu and the guest os. However, we want to create a consistent snapshot, so you can revert to the disk snapshot and get a consistent file system state. We also want to create a complete vm snapshot, including all disks and vm memory. Libvirt and qemu provides that when given a new disk for the active layer, but when using ceph disk, we don't change the active layer - we continue to use the same disk. Since 1.2.5, libvirt provides virDomainFSFreeze and virDomainFSThaw: https://libvirt.org/hvsupport.html So here is possible flows (ignoring engine side stuff like locking vms and disks) Disk snapshot ------------- 1. Engine invoke VM.freezeFileSystems 2. Vdsm invokes libvirt.virDomainFSFreeze 3. Engine creates snapshot via cinder 4. Engine invokes VM.thawFileSystems 5. Vdsm invokes livbirt.virDomainFSThaw Vm snapshot ----------- 1. Engine invoke VM.freezeFileSystems 2. Vdsm invokes libvirt.virDomainFSFreeze 3. Engine creates snapshot via cinder 4. Engine invokes VM.snapshot 5. Vdsm creates snapshot, skipping ceph disks 6. Engine invokes VM.thawFileSystems 7. Vdsm invokes livbirt.virDomainFSThaw API changes ----------- New verbs: - VM.freezeFileSystems - basically invokes virDomainFSFreeze - VM.thawFileSystems - basically invokes virDomainFSThaw What do you think? Nir

4 5

Dropping Fedora 20 builds on master / 3.6 in 2 weeks
by Sandro Bonazzola 25 Jun '15

25 Jun '15

Hi, now that we have Wildfly support for oVirt engine and Fedora 20 reached the end of its life, it's time to drop Fedora 20 builds on master. We'll keep building for Fedora 20 on the 3.5 branch since we don't support Wildfly there. If you're still developing or testing oVirt master on Fedora 20 please upgrade to Fedora 22 in the next 2 weeks. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[UI] New Domain dialog broken
by Piotr Kliczewski 25 Jun '15

25 Jun '15

Hi, I rebuilt the engine master today and get following error when opening a dialog to add storage domain: Can someone please take a look? Thanks, Piotr Thu Jun 25 14:49:01 GMT+200 2015 SEVERE: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) __gwt$exception: <skipped>: Tab(...) is undefined at Unknown.Akv(Unknown Source) at Unknown.Mjf(Unknown Source) at Unknown.Pjf(Unknown Source) at Unknown.Njf(Unknown Source) at Unknown.Xjf(Unknown Source) at Unknown.bhk(Unknown Source) at Unknown.dhk(Unknown Source) at Unknown.zY(Unknown Source) at Unknown.Rkv(Unknown Source) at Unknown.zY(Unknown Source) at Unknown.Hkv(Unknown Source) at Unknown.Sgk(Unknown Source) at Unknown.rkv(Unknown Source) at Unknown.vkv(Unknown Source) at Unknown.fsv(Unknown Source) at Unknown.usv(Unknown Source) at Unknown.$jr(Unknown Source) at Unknown.U5n(Unknown Source) at Unknown.feq(Unknown Source) at Unknown.$jr(Unknown Source) at Unknown.U5n(Unknown Source) at Unknown.o6n(Unknown Source) at Unknown.bhk(Unknown Source) at Unknown.thk(Unknown Source) at Unknown.$jr(Unknown Source) at Unknown.S5n(Unknown Source) at Unknown.n6n(Unknown Source) at Unknown.m6n(Unknown Source) at Unknown.O3p(Unknown Source) at Unknown.T3p(Unknown Source) at Unknown.P3p(Unknown Source) at Unknown.$5p(Unknown Source) at Unknown.Y5p(Unknown Source) at Unknown.Z5p(Unknown Source) at Unknown.j6p(Unknown Source) at Unknown.rvn(Unknown Source) at Unknown.uvn(Unknown Source) at Unknown.lzn(Unknown Source) at Unknown.ozn(Unknown Source) at Unknown.jyn(Unknown Source) at Unknown.myn(Unknown Source) at Unknown.RBe(Unknown Source) at Unknown.Rhk(Unknown Source) at Unknown.M3(Unknown Source) at Unknown.d4(Unknown Source) at Unknown.Lof/c.onreadystatechange<(Unknown Source) at Unknown.Xt(Unknown Source) at Unknown._t(Unknown Source) at Unknown.$t/<(Unknown Source) at Unknown.anonymous(Unknown Source) http://localhost:8080/ovirt-engine/webadmin/76B50B2E63805C707DBDD2E6CC5344F… Line 23283

2 2

[vdsm][mom][jsonrpc] new VDSM interface for MOM
by Francesco Romani 25 Jun '15

25 Jun '15

Hi everyone, I'm working to brush up and enhance my old hack https://gerrit.ovirt.org/#/c/37827/1 That patch adds a new MOM interface, to talk with VDSM using the RPC interface. On top of that, I want to make efficient use of VDSM API (avoid redundant call, possibly issuing only one getAllVmStats call and caching the results, and so forth) Next step will be to backport optimizations to current vdsmInterface. Or maybe, even replacing the new vdsminterface with the new one I'm developing :) I'd like to use the blessed JSON-RPC interface, but what's the recommended way to do that? What is (or will be!) the official recommended VDSM external client interface? I thought about patch https://gerrit.ovirt.org/#/c/39203/ But my _impression_ is that patch will depend on VDSM's internal reactor, thus is not very suitable to be used into an external process. -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

4 6

error starting engine on wildfly 8.2 fedora 22
by Greg Sheremeta 24 Jun '15

24 Jun '15

Hey, Can't seem to get engine started. Any ideas? Did I miss a step? I'm on latest master (4dd3093d42fd2c5826c941b7e19176a0e657a43f). Fresh engine directory, fresh database. Fedora 22. greg@dauntless:~/projects/ovirt-engine(master2|✔) % ovirt_run OpenJDK 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0 OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Listening for transport dt_socket at address: 8787 .... 2015-06-24 13:31:01,719 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deploym ent.unit."engine.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."engine.ear".WeldStart Service: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2 .2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] Caused by: org.jboss.weld.exceptions.DefinitionException: 0 at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:182) at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:166) at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:158) at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:230) at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:373) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:91) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] ... 3 more Caused by: java.lang.ArrayIndexOutOfBoundsException: 0 at org.hibernate.validator.internal.util.ExecutableHelper.instanceMethodParametersResolveToSameTypes(ExecutableHelper.java:141) at org.hibernate.validator.internal.util.ExecutableHelper.overrides(ExecutableHelper.java:101) at org.hibernate.validator.internal.cdi.ValidationExtension.replaceWithOverriddenOrInterfaceMethod(ValidationExtension.java:425) at org.hibernate.validator.internal.cdi.ValidationExtension.determineConstrainedMethod(ValidationExtension.java:275) at org.hibernate.validator.internal.cdi.ValidationExtension.determineConstrainedCallables(ValidationExtension.java:262) at org.hibernate.validator.internal.cdi.ValidationExtension.processAnnotatedType(ValidationExtension.java:242) at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) [:1.8.0_45] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45] at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45] at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271) at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237) at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174) at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:112) at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:180) ... 11 more 2015-06-24 13:31:01,729 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"engine.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"engine.ear\".WeldStartService: Failed to start service Caused by: org.jboss.weld.exceptions.DefinitionException: 0 Caused by: java.lang.ArrayIndexOutOfBoundsException: 0"}} 2015-06-24 13:31:01,764 INFO [org.jboss.as.server] (ServerService Thread Pool -- 20) JBAS018559: Deployed "engine.ear" (runtime-name : "engine.ear") 2015-06-24 13:31:01,764 INFO [org.jboss.as.server] (ServerService Thread Pool -- 20) JBAS018559: Deployed "legacy_restapi.war" (runtime-name : "legacy_restapi.war") 2015-06-24 13:31:01,764 INFO [org.jboss.as.server] (ServerService Thread Pool -- 20) JBAS018559: Deployed "restapi.war" (runtime-name : "restapi.war") 2015-06-24 13:31:01,765 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."engine.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."engine.ear".WeldStartService: Failed to start service 2015-06-24 13:31:01,804 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:8706/management 2015-06-24 13:31:01,804 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:8706 2015-06-24 13:31:01,804 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 8766ms - Started 1046 of 1201 services (52 services failed or missing dependencies, 177 services are lazy, passive or on-demand) 2015-06-24 13:31:02,016 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017535: Unregistered web context: /api 2015-06-24 13:31:02,016 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /ovirt-engine/api 2015-06-24 13:31:02,017 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /ovirt-engine/webadmin 2015-06-24 13:31:02,016 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017535: Unregistered web context: / 2015-06-24 13:31:02,016 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /ovirt-engine/userportal 2015-06-24 13:31:02,019 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /ovirt-engine/docs 2015-06-24 13:31:02,020 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017535: Unregistered web context: /ovirt-engine ... greg@dauntless:~/ovirt-engine/var/log/ovirt-engine % dnf list installed |grep -i weld Repository patternfly-patternfly-test is listed more than once in the configuration weld-api.noarch 2.1-3.fc21 @System weld-core.noarch 2.1.2-4.fc22 @System weld-parent.noarch 26-3.fc21 @System greg@dauntless:~/ovirt-engine/var/log/ovirt-engine % dnf list installed |grep -i wildfly Repository patternfly-patternfly-test is listed more than once in the configuration ovirt-engine-wildfly.x86_64 8.2.0-1.fc22 @System ovirt-engine-wildfly-overlay.noarch 001-2.fc22 @System wildfly.noarch 8.1.0-3.fc22 @System wildfly-security-manager.noarch 1.0.0-2.fc21 @System Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

2 2

[ATN][devenv] Please update otopi/ovirt-host-deploy to latest master
by Alon Bar-Lev 24 Jun '15

24 Jun '15

Hi, Due to recent additions of serial console, please make sure all devs update otopi/ovirt-host-deploy to latest master snapshot at resources.ovirt.org. Thanks!

1 0

oVirt has just moved to WildFly 8.2
by Martin Perina 24 Jun '15

24 Jun '15

Hi, all WildFly related patches were merged, so at the moment for engine development you need special version of WildFly 8.2 provided by these packages: ovirt-engine-wildfly-8.2.0-1 ovirt-engine-wildfly-overlay-001-2 Please update you development environment according to information we posted in previous email [1]. Don't hesitate to contact me or any other infra team member with any issues you may have with the update. I would like to thank Juan for his original WildFly patches and especially for his hard work to make RESTAPI compatible with WildFly. I would also like to thank Yevgeny and Moti for help with CDI patches, Alon and Sandro for help with packaging and Python related stuff, Ori for help with RESTAPI patches, Dima for help with System Testing Framework, Eyal and Max for help with developer job and Oved for great advices and putting all things together. Thanks Martin Perina [1] http://lists.ovirt.org/pipermail/devel/2015-June/010832.html

1 0

cannot install host: VdsDeployBase, Error during deploy dialog: java.lang.NullPointerException
by Martin Mucha 24 Jun '15

24 Jun '15

Hi, I have difficulties to install host. I do believe it fails due to this: 2015-06-24 08:29:26,729 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [612066b7] Error during deploy dialog: java.lang.NullPointerException at org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236) [otopi.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeploy$43.call(VdsDeploy.java:579) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeploy$43.call(VdsDeploy.java:577) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase._nextCustomizationEntry(VdsDeployBase.java:202) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase._threadMain(VdsDeployBase.java:301) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.access$200(VdsDeployBase.java:45) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase$7.run(VdsDeployBase.java:392) [bll.jar:] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] anyone met this? Know how to overcome this? Any hints welcomed. (alredy tried to remove library from m2 repo to force re-download) M.

3 3