- Users - oVirt List Archives

Unable to import template from export domain Ovirt 3.6
by Liam Curtis 12 Nov '15

12 Nov '15

Able to create a template on one host, and then export to NFS. I detach from one host and successfully attach to second host. WHen I attempt to import template, I see error 'Failed to complete copy of template mytemplate to Domain <UNKNOWN>' Errors in log are: 2015-11-08 20:08:26,516 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-28) [9f0aa95] Correlation ID: d957f05, Job ID: 084199b0-96ce-4b80-bd02-a0d45bcd5de9, Call Stack: null, Custom Event ID: -1, Message: Failed to import Template mytemplate to Data Center ovirt-2_localdc, Cluster ovirt-2_localclstr 2015-11-08 20:08:29,329 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-50) [] Correlation ID: d957f05, Call Stack: null, Custom Event ID: -1, Message: Failed to complete copy of Template mytemplate to Domain <UNKNOWN>. Seeing this command that failed: 2015-11-08 20:08:29,296 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler_Worker-76) [395116d1] BaseAsyncTask::logEndTaskFailure: Task 'd2681280-fff6-469d-81c8-edc5fd9fb7af' (Parent Command 'ImportVmTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: -- Message: 'VDSGenericException: VDSErrorException: Failed in vdscommand to HSMGetAllTasksStatusesVDS, error = d2681280-fff6-469d-81c8-edc5fd9fb7af', -- Exception: 'VDSGenericException: VDSErrorException: Failed in vdscommand to HSMGetAllTasksStatusesVDS, error = d2681280-fff6-469d-81c8-edc5fd9fb7af' But dont see anything else... Thoughts?

3 6

upgrade to oVirt 3.6 and compabitibility 3.6
by Paul Groeneweg | Pazion 12 Nov '15

12 Nov '15

I have finished the upgrade to 3.6. I received a lot (every 3 seconds ) of the following messages in the logs after upgrading the hosts: vdsm jsonrpc.JsonRpcServer ERROR Internal server error#012Traceback (most recent call last):#012 File "/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py", line 501, in _serveRequest#012 res = method(**params)#012 File "/usr/share/vdsm/rpc/Bridge.py", line 291, in _dynamicMethod#012 return self._fixupRet(className, methodName, ret)#012 File "/usr/share/vdsm/rpc/Bridge.py", line 235, in _fixupRet#012 self._typeFixup('return', retType, result)#012 File "/usr/share/vdsm/rpc/Bridge.py", line 215, in _typeFixup#012 if k in item:#012TypeError: argument of type 'NoneType' is not iterable I restarted ovirt-ha-agent ovirt-ha-broker and vdsmd. After I rebooted all hosts ( migrating VMS from one to another ) the message finally disappeared. Then I tried to set compatibility Version to 3.6, but without luck. I have put hosted engine back in global maintenance, but I can't find out why it fails. The message says "Error while executing action: Cannot change Cluster Compatibility Version to higher version when there are active Hosts with lower version. -Please move Hosts with lower version to maintenance first." I have installed ovirt-release36 on hosted engine and hosts. I have updated hosted engine with engine-setup. I ran yum update on all hosts. What do I need to do to set compatibility version to 3.6? And how can I enable repository for hosted engine? ( through WEB UI change is not saved ). Best Regards, Paul Groeneweg -- Met vriendelijke groeten, Paul Groeneweg Pazion Webdevelopment - Hosting - Apps T +31 26 3020038 M +31 614 277 577 E paul(a)pazion.nl ***disclaimer*** "This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation."

4 14

_initialize_sanlock cannot get lock, host already holds lock on a different host id
by Robert Story 12 Nov '15

12 Nov '15

--Sig_/.6C2e=H_BL1+iV=uP1v2/O5 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I'm running oVirt 3.5.x with a hosted engine. On 3 of my 5 nodes, ovirt-ha-agent won't start, complaining that "(_initialize_sanlock) cannot get lock on host id 5: host already holds lock on a different host id." Running 'grep host_id /etc/ovirt-hosted-engine/hosted-engine.conf' on each host shows that they all have different unique ids, 1-5. How can I debug this? Is there a command I can run to see which host holds a sanlock for each id? Robert --=20 Senior Software Engineer @ Parsons --Sig_/.6C2e=H_BL1+iV=uP1v2/O5 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWRJtSAAoJEMHFVuy5l8Y4T+EQAKbWkcTuXrUIP4V/JcDKXp+k nVp6VATvbX9AImdyW16QK+k5b/AMRRMhuo+0/vwmSo9iLst1Hf2fGf78ydSB8nj4 d3k+hMSjsJrFajL79iECd9izX9l3BB63pp02Ako0sxDjRzQOOuFTYQnNfX1Pt2V7 Tq7K1im3N2gVjVsBB0bDxC7bVPNpxHR1Jt6uKOUHE0pnWAGKsgOqqZtFhr4yNQHw C7k0+Qx6yuiqQnnRi0KmN0XaHMlZVqBwkCB9IuKj7l6akWIwsqYivOobm3fWgrzl vdy6EIKq6/tZdZvyPqtm2LkvdfAujIx0294xkiuMvGDaXjYQynhITro8P/EvAk1z XqEPmxCzSHZdT9gGe2Xw5jUKNrb4UO4H82uoWkyuibXGCR6ezPDINFmwaZ1kl7mo 5D+D8DioJaUVlfzFN+s9XxrKGpaJZ6FM+P7wsrfwK5W29jCa43sAxquPdsRVxQFU JYLzF0n+1B+1jtFnz2Ok3X57dHxEgy1i/QgWz/3vTGolD+r2lIxDCkbxdrrMVeMN 6/9bWp4Ki//5hEflZEbqCFWfZNgh+F3dXu2oZ55vleej8o5n/nbbb+7vV2v9BWjP osIHvhon39AEyMAIPFAttvxPbTMNVw8Uw45LFGkHuhr0NlNqEfUCMT+j/MFoeTlR KI/VAxFT/evusA8MRGxF =I+CF -----END PGP SIGNATURE----- --Sig_/.6C2e=H_BL1+iV=uP1v2/O5--

2 3

Centos 7.1 failed to start glusterd after upgrading to ovirt 3.6
by Stefano Danzi 12 Nov '15

12 Nov '15

After upgrading oVirt from 3.5 to 3.6, glusterd fail to start when the host boot. Manual start of service after boot works fine. gluster log: [2015-11-04 13:37:55.360876] I [MSGID: 100030] [glusterfsd.c:2318:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.7.5 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid) [2015-11-04 13:37:55.447413] I [MSGID: 106478] [glusterd.c:1350:init] 0-management: Maximum allowed open file descriptors set to 65536 [2015-11-04 13:37:55.447477] I [MSGID: 106479] [glusterd.c:1399:init] 0-management: Using /var/lib/glusterd as working directory [2015-11-04 13:37:55.464540] W [MSGID: 103071] [rdma.c:4592:__gf_rdma_ctx_create] 0-rpc-transport/rdma: rdma_cm event channel creation failed [Nessun device corrisponde] [2015-11-04 13:37:55.464559] W [MSGID: 103055] [rdma.c:4899:init] 0-rdma.management: Failed to initialize IB Device [2015-11-04 13:37:55.464566] W [rpc-transport.c:359:rpc_transport_load] 0-rpc-transport: 'rdma' initialization failed [2015-11-04 13:37:55.464616] W [rpcsvc.c:1597:rpcsvc_transport_create] 0-rpc-service: cannot create listener, initing the transport failed [2015-11-04 13:37:55.464624] E [MSGID: 106243] [glusterd.c:1623:init] 0-management: creation of 1 listeners failed, continuing with succeeded transport [2015-11-04 13:37:57.663862] I [MSGID: 106513] [glusterd-store.c:2036:glusterd_restore_op_version] 0-glusterd: retrieved op-version: 30600 [2015-11-04 13:37:58.284522] I [MSGID: 106194] [glusterd-store.c:3465:glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps list. [2015-11-04 13:37:58.287477] E [MSGID: 106187] [glusterd-store.c:4243:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore [2015-11-04 13:37:58.287505] E [MSGID: 101019] [xlator.c:428:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2015-11-04 13:37:58.287513] E [graph.c:322:glusterfs_graph_init] 0-management: initializing translator failed [2015-11-04 13:37:58.287518] E [graph.c:661:glusterfs_graph_activate] 0-graph: init failed [2015-11-04 13:37:58.287799] W [glusterfsd.c:1236:cleanup_and_exit] (-->/usr/sbin/glusterd(glusterfs_volumes_init+0xfd) [0x7f29b876524d] -->/usr/sbin/glusterd(glusterfs_process_volfp+0x126) [0x7f29b87650f6] -->/usr/sbin/glusterd(cleanup_and_exit+0x69) [0x7f29b87646d9] ) 0-: received signum (0), shutting down

4 7

oVirt hosts and yum updates
by Robert Story 12 Nov '15

12 Nov '15

--Sig_/Z2=7wOKtRMuJTrd_zNJl4ws Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I was wondering what other folks do to keep their oVirt hosts up to date, both with the base OS pacakges and oVirt packages.Is it safe to enable yum-cron? I'm concerned that it might cause issues if vdsm/ovirt packages are updated without following the correct procedure, but would like other OS packages to be kept up to date. Robert --=20 Senior Software Engineer @ Parsons --Sig_/Z2=7wOKtRMuJTrd_zNJl4ws Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWRJLJAAoJEMHFVuy5l8Y4+DoP/jx2yKrqDTd7u+W1T1NGXvtZ fhKN3+yGcH2OVXCliaoSEO0XZJweub+3QOE52KgL6ErnK1kU/QvCQYpeGNIJvAXW 5YmCh7cuFQzowqZ0tLQ5Fvg86uqbYfsMpxdSFl/IJUZbHyBOCylV6fDV1Ogobl1R GwQQcU85wbZQrGHLUfV1vAqIQEvzspSV0F0OZODGVbHdq/qOEKgOpWg3Xl644TNI hn29MV+CqVEsRANzRs2SKbt4Dem4Q+feDPhkNw8gaUmbfnzYRWlj+ysVqZge2y1i 4XPabtCr0VRXaR5kjmo0fvwUenIWFbtioEXqbsGFz6U5XoKoxBLU/qANGEaBN5kd svn6oPmGldaHGtcZAbJIdyVfgTYJjmUOoITUUDQs74Y6z8duazX6TAmxW1+NldJj /3JQs4H6jxD+Wltm+ldI6KEyFBuFX7czaZvGNj50/Hd8P8/8VF7gBtx64zSfBO3E HdxTcPnv70zkZWqUtYrx1ed3XeiTtP8W8OKs5zKD1OXbiS6aY99vTKVpCGkf3doG tCjhiUicblTf6Fkm4sVGuPltx1wok6XUVEUJWWDR1nToMoshSabAYD4XPgOKJUrr p5aXDv+lojkThUcPTf5Ie861tW8rij+dlmMCS6Nb9OHznyPGCGxrdYmlqix5mcJQ u4Q4uQ1o5YEQ77TOPhL5 =OSzT -----END PGP SIGNATURE----- --Sig_/Z2=7wOKtRMuJTrd_zNJl4ws--

2 1

Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
by David Marzal Canovas 12 Nov '15

12 Nov '15

Hi Sandro, thanks for the tips. After a few problems, I think everything is working OK. I already had an image of my server so I tried the path that you suggested and this is what I found: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm fedup --network 22 --product=server This show a warning but the upgrade is successful : WARNING: potential problems with upgrade ovirt-engine-backend-3.5.4.2-1.fc20.noarch (no replacement) requires vdsm-jsonrpc-java-1.0.15-1.fc20.noarch (replaced by vdsm-jsonrpc-java-1.1.5-1.fc22.noarch) ovirt-engine-3.5.4.2-1.fc20.noarch (no replacement) requires 1:java-1.7.0-openjdk-1.7.0.79-2.5.5.0.fc20.x86_64 (replaced by 1:java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64) Continue with the upgrade at your own risk. After reboot the system is upgraded but perl is broken due to some packages not being up to date. This can be fixed with (after allowing dnf in the firewall ) dnf distro-sync --setopt=deltarpm=0 Upgrade the DB and change the configuration (ovirt 3.6 needs lc_messages = 'en_US.UTF-8' ) postgresql-setup --upgrade vim /var/lib/pgsql/data/postgresql.conf /var/lib/pgsql/data/pg_hba.conf Check the rest of configuration files rpmconf -a Then check the services because nfs has some bug and dies on startup https://bugzilla.redhat.com/show_bug.cgi?id=1192501 https://bugzilla.redhat.com/show_bug.cgi?id=1178720 systemctl status postgresql.service nfs until you execute systemctl enable nfs-server.service And now we finally can upgrade oVirt engine-setup It will show a warning about versionlock: DNF Failed loading plugin: versionlock But it would upgrade oVirt correctly. At my first attempt I don't have any problem with the fedup --network 22 --product=server but I didn't modify all the necessary files and fix the nfs so at one pont y restore the image of the server and start over. In the second attempt (the next day) the command complaint about ovirt-release35-006-1 Downloading failed: El paquete ovirt-release35-006-1.noarch.rpm no está firmado (is not signed) I had to remove this package and the files on /etc/yum.repos.d to be able to upgrade Fedora to 22 yum remove ovirt-release35 rm /etc/yum.repos.d/ovirt-3.5* I also test before trying to use fedup to just yum upgrade the system but end with the same error so finally I delete ovirt-release35 and could continue with the process described. I hope this is useful if someone needs to upgrade their systems. And thanks for an incredible product. :) PD: Sorry for the (lack of) formating

2 1

OVIRT Roadmap for 2016
by Rizwan Ashraf 12 Nov '15

12 Nov '15

------=_Part_1835611_1951878609.1447267970840 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Dear all, I am interested to learn about activity and approach for 2016 OVIRT roadmap. Perhaps features scope of OVIRT 3.7? Thank you and best regards, Riz ------=_Part_1835611_1951878609.1447267970840 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1447257745568_24380">Dear all,</div><div id="yui_3_16_0_1_1447257745568_24230"><br></div><div dir="ltr" id="yui_3_16_0_1_1447257745568_24231">I am interested to learn about activity and approach for 2016 OVIRT roadmap. <br></div><div id="yui_3_16_0_1_1447257745568_24401" dir="ltr"><br></div><div id="yui_3_16_0_1_1447257745568_24402" dir="ltr">Perhaps features scope of OVIRT 3.7?</div><div id="yui_3_16_0_1_1447257745568_24395" dir="ltr"><br></div><div id="yui_3_16_0_1_1447257745568_24399" dir="ltr">Thank you and best regards,</div><div id="yui_3_16_0_1_1447257745568_24396" dir="ltr"><br></div><div id="yui_3_16_0_1_1447257745568_24397" dir="ltr">Riz<br></div><div id="yui_3_16_0_1_1447257745568_24232"><br></div></div></body></html> ------=_Part_1835611_1951878609.1447267970840--

3 2

Fwd: Reminder: Fedora 21 end of life on 2015-12-01
by Sandro Bonazzola 12 Nov '15

12 Nov '15

FYI oVirt Fedora 21 support will end as well. ---------- Forwarded message ---------- From: Kevin Fenzi <kevin(a)scrye.com> Date: Tue, Nov 10, 2015 at 4:24 PM Subject: Reminder: Fedora 21 end of life on 2015-12-01 To: devel-announce(a)lists.fedoraproject.org, test-announce(a)lists.fedoraproject.org, announce(a)lists.fedoraproject.org Greetings. This is a reminder email about the end of life process for Fedora 21. Fedora 21 will reach end of life on 2015-12-01, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 23, no new packages will be added to the Fedora 21 collection. Please see https://fedoraproject.org/wiki/DNF_system_upgrade for more information on upgrading from Fedora 21 to a newer release. kevin _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- 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 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Update on oVirt Mirroring Status
by Anton Marchukov 12 Nov '15

12 Nov '15

Hello All. Following previous announcement, please note that we still face a problem with getting updates to our mirrors. This is firewalling problem and we are working with IT on resolving it. I have temporarily updated mirror list to include only resources.ovirt.org there. It will be changed back as soon as the mirroring is restored. Please note that if you are not using the mirrorlist and include URLs directly and you are interested in latest snapshoots, than you may need to use http://resources.ovirt.org/pub/ovirt-@VERSION@/rpm/@DIST@/ directly. Will reply on this message once I get an ETA. Please contact infra(a)ovirt.org in case you have any questions. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

1 1

Issue with ISO Domain
by Conteh, Modou 12 Nov '15

12 Nov '15

--_000_765A6D1C68C0AA4E8174B3A0E604BD75675E272CS04MBX0106s04lo_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am currently trying out OVirt in my organization as a vdi solution, but I= do have an issue after installation of the engine and the node, trying to = add the iso to the engine,I receive and error that, there is no iso domain= available, there is no documentation that actually touches on how to add I= SO images to the ISO domain, where is the ISO repo folder location, how can= one copy iso's to the domain. Also is it not possible to browse after set= ting up vm to pick from ones desktop an iso image to run for installing a v= m ? Thanks to everyone who is putting their effort in this project, we do appre= ciate you all Thanks --_000_765A6D1C68C0AA4E8174B3A0E604BD75675E272CS04MBX0106s04lo_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">I am currently trying out OVirt in my organization a= s a vdi solution, but I do have an issue after installation of the engine a= nd the node, trying to add the iso to the engine,I receive and error that, =  there is no iso domain available, there is no documentation that actually touches on how to add ISO images t= o the ISO domain, where is the ISO repo folder location, how can one copy i= so’s to the domain.  Also is it not possible to browse after set= ting up vm to pick from ones desktop an iso image to run for installing a vm ?<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Thanks to everyone who is putting their effort in th= is project, we do appreciate you all<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Thanks<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </body> </html> --_000_765A6D1C68C0AA4E8174B3A0E604BD75675E272CS04MBX0106s04lo_--

3 2