February 2014 - Users - oVirt List Archives

[Users] oVirt upcoming release schedule update
by Sandro Bonazzola 18 Feb '14

18 Feb '14

oVirt team has updated the release schedule for upcoming releases. These are tentative planning dates and may change. 2014-02-18 - oVirt 3.4.0 beta3 2014-02-18 - oVirt 3.3.4 beta 2014-02-24 - oVirt 3.4.0 RC Build 2014-02-25 - oVirt 3.3.4 RC 2014-02-27 - oVirt 3.4 Third Test Day 2014-03-03 - oVirt 3.4.0 GA 2014-03-04 - oVirt 3.3.4 GA 2014-05-01 - oVirt 3.5.0 Feature Freeze 2014-05-15 - oVirt 3.5.0 stable branching 2014-07-01 - oVirt 3.5.0 GA More details on test days, etc to come in the next few weeks. You'll find an updated ICS calendar attached to this email. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Postponing 3.4.0 RC and test day
by Sandro Bonazzola 18 Feb '14

18 Feb '14

Hi, we're postponing 3.4.0 RC build and test day to next week due to recent blockers opened on 3.4.0. We actually have bug count 361 out of which 19 urgent, 64 high. We're going to build a 3.4.0 beta3 later today once Bug 1066466 - Disk name doesn't get assigned automatically after a CREATE command. will be fixed. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Python SDK - VNIC profiles collection is missing under root
by Genadi Chereshnya 18 Feb '14

18 Feb '14

Hi, We installed the new ovirt-engine-sdk-python from Fedora repo - version 3.3.0.7-1.fc20 The VNIC profile collection was missing under API root. Installing it from nightly (version ovirt-engine-sdk-python-3.5.0.0-1.20140211.git61ac75b.fc20.noarch) had the same result. According to changelog (http://wiki.ovirt.org/Python-sdk-changelog) it was supposed to work from 3.3.0.4-1 Last time it was working was on 3.3.3-0.1 version. Thanks, Genadi

1 1

[Users] Very Triccky Video setting
by Juan Carlos YJ. Lin 17 Feb '14

17 Feb '14

--=_b2de6dc8-03a4-446a-ae26-3b665ae38574 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit I try to setup video mode to access by xrdp, and finda that is not possible to change video ram, vram sizes. find out hook qemu_cmdline that enable pass cmd line to qemu, but still is not running. I need to set the video to 1024x768 16 bits and refresh rate to 30 Please help Juan Carlos Lin Unisoft S.A. +595-993-288330 --------------------------------------------------- "Antes de imprimir, recuérdese de su compromiso con el Medio Ambiente" "Aviso: Este mensaje es dirigido para su destinatario y contiene informaciones que no pueden ser usadas por otras personas que no sean su(s) destinatario(s). La retransmisión del contenido no está autorizada fuera del contexto de su envío y a quien corresponde. El uso no autorizado de la información en este mensaje se halla penado por las leyes vigentes en todo el mundo. Si ha recibido este mensaje por error, por favor bórrala y notifique al remitente en la brevedad posible. El contenido de este mensaje no es responsabilidad de la Empresa y debe ser atribuido siempre a su autor. Gracias." --=_b2de6dc8-03a4-446a-ae26-3b665ae38574 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 10pt; color: #000000'>I try to setup video mode to access by xrdp, and finda that is not possible to change video ram, vram sizes. find out hook qemu_cmdline that enable pass cmd line to qemu, but still is not running. I need to set the video to 1024x768 16 bits and refresh rate to 30 Please help Juan Carlos Lin Unisoft S.A. +595-993-288330 </div> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <HTML lang="es"> <HEAD> <TITLE>System-wide Disclaimer</TITLE> </HEAD> <BODY>--------------------------------------------------- "Antes de imprimir, recuérdese de su compromiso con el Medio Ambiente" "Aviso: Este mensaje es dirigido para su destinatario y contiene informaciones que no pueden ser usadas por otras personas que no sean su(s) destinatario(s). La retransmisión del contenido no está autorizada fuera del contexto de su envío y a quien corresponde. El uso no autorizado de la información en este mensaje se halla penado por las leyes vigentes en todo el mundo. Si ha recibido este mensaje por error, por favor bórrala y notifique al remitente en la brevedad posible. El contenido de este mensaje no es responsabilidad de la Empresa y debe ser atribuido siempre a su autor. Gracias." </BODY> </HTML> </body></html> --=_b2de6dc8-03a4-446a-ae26-3b665ae38574--

1 0

[Users] "Volume Group does not exist". Blame device-mapper ?
by Nicolas Ecarnot 17 Feb '14

17 Feb '14

Hi, oVirt 3.3, no big issue since the recent snapshot joke, but all in all running fine. All my VM are stored in a iSCSI SAN. The VM usually are using only one or two disks (1: system, 2: data) and it is OK. Friday, I created a new LUN. Inside a VM, I linked to it via iscsiadm and successfully login to the Lun (session, automatic attach on boot, read, write) : nice. Then after detaching it and shuting down the MV, and for the first time, I tried to make use of the feature "direct attach" to attach the disk directly from oVirt, login the session via oVirt. I connected nice and I saw the disk appear in my VM as /dev/sda or whatever. I was able to mount it, read and write. Then disaster stoke all this : many nodes suddenly began to become unresponsive, quickly migrating their VM to the remaining nodes. Hopefully, the migrations ran fine and I lost no VM nor downtime, but I had to reboot every concerned node (other actions failed). In the failing nodes, /var/log/messages showed the log you can read in the end of this message. I first get device-mapper warnings, then the host unable to collaborate with the logical volumes. The 3 volumes are the three main storage domains, perfectly up and running where I store my oVirt VMs. My reflexions : - I'm not sure device-mapper is to blame. I frequently see device mapper complaining and nothing is getting worse (not oVirt specifically) - I have not change my network settings for months (bonding, linking...) The only new factor is the usage of direct attach LUN. - This morning I was able to reproduce the bug, just by trying again this attachement, and booting the VM. No mounting of the LUN, just VM booting, waiting, and this is enough to crash oVirt. - when the disaster happens, usually, amongst the nodes, only three nodes gets stroke, the only one that run VMs. Obviously, after migration, different nodes are hosting the VMs, and those new nodes are the one that then get stroke. This is quite reproductible. And frightening. The log : Jan 20 10:20:45 serv-vm-adm11 kernel: device-mapper: table: 253:36: multipath: error getting device Jan 20 10:20:45 serv-vm-adm11 kernel: device-mapper: ioctl: error adding target to table Jan 20 10:20:45 serv-vm-adm11 kernel: device-mapper: table: 253:36: multipath: error getting device Jan 20 10:20:45 serv-vm-adm11 kernel: device-mapper: ioctl: error adding target to table Jan 20 10:20:47 serv-vm-adm11 vdsm TaskManager.Task ERROR Task=`847653e6-8b23-4429-ab25-257538b35293`::Unexpected error#012Traceback (most recent call last):#012 File "/usr/share/vdsm/storage/task.py", line 857, in _run#012 return fn(*args, **kargs)#012 File "/usr/share/vdsm/logUtils.py", line 45, in wrapper#012 res = f(*args, **kwargs)#012 File "/usr/share/vdsm/storage/hsm.py", line 3053, in getVolumeSize#012 volUUID, bs=1))#012 File "/usr/share/vdsm/storage/volume.py", line 333, in getVSize#012 mysd = sdCache.produce(sdUUID=sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 98, in produce#012 domain.getRealDomain()#012 File "/usr/share/vdsm/storage/sdc.py", line 52, in getRealDomain#012 return self._cache._realProduce(self._sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 122, in _realProduce#012 domain = self._findDomain(sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 141, in _findDomain#012 dom = findMethod(sdUUID)#012 File "/usr/share/vdsm/storage/blockSD.py", line 1288, in findDomain#012 return BlockStorageDomain(BlockStorageDomain.findDomainPath(sdUUID))#012 File "/usr/share/vdsm/storage/blockSD.py", line 414, in __init__#012 lvm.checkVGBlockSizes(sdUUID, (self.logBlkSize, self.phyBlkSize))#012 File "/usr/share/vdsm/storage/lvm.py", line 976, in checkVGBlockSizes#012 raise se.VolumeGroupDoesNotExist("vg_uuid: %s" % vgUUID)#012VolumeGroupDoesNotExist: Volume Group does not exist: ('vg_uuid: 1429ffe2-4137-416c-bb38-63fd73f4bcc1',) Jan 20 10:20:47 serv-vm-adm11 ¿<11>vdsm vm.Vm ERROR vmId=`2c0bbb51-0f94-4bf1-9579-4e897260f88e`::Unable to update the volume 80bac371-6899-4fbe-a8e1-272037186bfb (domain: 1429ffe2-4137-416c-bb38-63fd73f4bcc1 image: a5995c25-cdc9-4499-b9b4-08394a38165c) for the drive vda Jan 20 10:20:48 serv-vm-adm11 vdsm TaskManager.Task ERROR Task=`886e07bd-637b-4286-8a44-08dce5c8b207`::Unexpected error#012Traceback (most recent call last):#012 File "/usr/share/vdsm/storage/task.py", line 857, in _run#012 return fn(*args, **kargs)#012 File "/usr/share/vdsm/logUtils.py", line 45, in wrapper#012 res = f(*args, **kwargs)#012 File "/usr/share/vdsm/storage/hsm.py", line 3053, in getVolumeSize#012 volUUID, bs=1))#012 File "/usr/share/vdsm/storage/volume.py", line 333, in getVSize#012 mysd = sdCache.produce(sdUUID=sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 98, in produce#012 domain.getRealDomain()#012 File "/usr/share/vdsm/storage/sdc.py", line 52, in getRealDomain#012 return self._cache._realProduce(self._sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 122, in _realProduce#012 domain = self._findDomain(sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 141, in _findDomain#012 dom = findMethod(sdUUID)#012 File "/usr/share/vdsm/storage/blockSD.py", line 1288, in findDomain#012 return BlockStorageDomain(BlockStorageDomain.findDomainPath(sdUUID))#012 File "/usr/share/vdsm/storage/blockSD.py", line 414, in __init__#012 lvm.checkVGBlockSizes(sdUUID, (self.logBlkSize, self.phyBlkSize))#012 File "/usr/share/vdsm/storage/lvm.py", line 976, in checkVGBlockSizes#012 raise se.VolumeGroupDoesNotExist("vg_uuid: %s" % vgUUID)#012VolumeGroupDoesNotExist: Volume Group does not exist: ('vg_uuid: 1429ffe2-4137-416c-bb38-63fd73f4bcc1',) Jan 20 10:20:48 serv-vm-adm11 ¿<11>vdsm vm.Vm ERROR vmId=`2c0bbb51-0f94-4bf1-9579-4e897260f88e`::Unable to update the volume ea9c8f12-4eb6-42de-b6d6-6296555d0ac0 (domain: 1429ffe2-4137-416c-bb38-63fd73f4bcc1 image: f42e0c9d-ad1b-4337-b82c-92914153ff44) for the drive vdb Jan 20 10:21:03 serv-vm-adm11 vdsm TaskManager.Task ERROR Task=`27bb14f9-0cd1-4316-95b0-736d162d5681`::Unexpected error#012Traceback (most recent call last):#012 File "/usr/share/vdsm/storage/task.py", line 857, in _run#012 return fn(*args, **kargs)#012 File "/usr/share/vdsm/logUtils.py", line 45, in wrapper#012 res = f(*args, **kwargs)#012 File "/usr/share/vdsm/storage/hsm.py", line 3053, in getVolumeSize#012 volUUID, bs=1))#012 File "/usr/share/vdsm/storage/volume.py", line 333, in getVSize#012 mysd = sdCache.produce(sdUUID=sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 98, in produce#012 domain.getRealDomain()#012 File "/usr/share/vdsm/storage/sdc.py", line 52, in getRealDomain#012 return self._cache._realProduce(self._sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 122, in _realProduce#012 domain = self._findDomain(sdUUID)#012 File "/usr/share/vdsm/storage/sdc.py", line 141, in _findDomain#012 dom = findMethod(sdUUID)#012 File "/usr/share/vdsm/storage/blockSD.py", line 1288, in findDomain#012 return BlockStorageDomain(BlockStorageDomain.findDomainPath(sdUUID))#012 File "/usr/share/vdsm/storage/blockSD.py", line 414, in __init__#012 lvm.checkVGBlockSizes(sdUUID, (self.logBlkSize, self.phyBlkSize))#012 File "/usr/share/vdsm/storage/lvm.py", line 976, in checkVGBlockSizes#012 raise se.VolumeGroupDoesNotExist("vg_uuid: %s" % vgUUID)#012VolumeGroupDoesNotExist: Volume Group does not exist: ('vg_uuid: 83d39199-d4e4-474c-b232-7088c76a2811',) -- Nicolas Ecarnot

4 10

[Users] Command line : how to add a removed host?
by Nicolas Ecarnot 17 Feb '14

17 Feb '14

Hi, Doing some tests, I set 2 hosts into maintenance mode, then "removed" them. When trying to add them back into the cluster, I found nothing more than the "new" action. Using it and configuring the IP address, I see oVirt re-installing many packages. Once installed, the host can not be added because : "Host host016 is installed with VDSM version (4.13) and cannot join cluster cluster21 which is compatible with VDSM versions [4.9, 4.11, 4.12, 4.10]." In fact, I have 2 questions: - For the second host (still untouched), is there a way to add it back into the cluster without re-installing the packages maybe via the command line) (and then preventing this version issue)? - For the weeks to come, I see I'll have to upgrade some parts. I don't know what is needed to upgrade for the VDSM version to get upgraded ("for [4.9, 4.11, 4.12, 4.10] to increase"). Obviously, I don't want to break the whole cluster while upgrading it. Thank you. -- Nicolas Ecarnot

1 0

[Users] Stuck Migration
by Maurice James 17 Feb '14

17 Feb '14

------=_NextPart_000_007E_01CF27B5.A5C4DDA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I have a vm that is shut down and is somehow stuck in a migration state. Im running version 3.3.3-2 on this setup. The vm disk is activated and cannot be deactivated, and the vm is shut down and cannot be started. When I try to start the vm it tells me that it cannot be started because it is in the process of migrating ------=_NextPart_000_007E_01CF27B5.A5C4DDA0 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-microsoft-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=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 = (filtered medium)"><style></style></head><body lang=3DEN-US = link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1>I have a vm that is shut down and is somehow stuck in = a migration state. Im running version 3.3.3-2 on this setup. The vm disk = is activated and cannot be deactivated, and the vm is shut down and = cannot be started. When I try to start the vm it tells me that it cannot = be started because it is in the process of = migrating<o:p></o:p></div></body></html> ------=_NextPart_000_007E_01CF27B5.A5C4DDA0--

5 9

[Users] about live snapshot and qemu-kvm
by Nathanaël Blanchet 17 Feb '14

17 Feb '14

This is a multi-part message in MIME format. --------------080009080202040109020900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi all, I'm about to migrate from the dreyou 3.2 repo to the official 3.3 repositories. I was used to take live snapshot with qemu-kvm-rhev-0.12.1.2-2.355.el6.5.x86_64 which was recompiled from the redhat srpms, because live snapshot was not supported by the official qemu-kvm in el6.4. * Does now 6.5 include the correct qemu-kvm version for live snapshot? * If not why does redhat provide a separate qemu package for RHEV while fedora has got the correct package? * Does ovirt team provide support for el6 live snapshot "out of the box" or do they recommend to get the correct qemu-kvm version from the rhev repository? Assuming that redhat doesn't provide the same qemu-kvm in rhev than in el6, what about including qemu-kvm-rhev in the ovirt el6 repository as dreyou did ? Thanks -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr --------------080009080202040109020900 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, I'm about to migrate from the dreyou 3.2 repo to the official 3.3 repositories. I was used to take live snapshot with qemu-kvm-rhev-0.12.1.2-2.355.el6.5.x86_64 which was recompiled from the redhat srpms,  because live snapshot was not supported by the official qemu-kvm in el6.4. <ul> <li>Does now 6.5 include the correct qemu-kvm version for live snapshot?</li> <li>If not why does redhat provide a separate qemu package for RHEV while fedora has got the correct package? </li> <li>Does ovirt team provide support for el6 live snapshot "out of the box" or do they recommend to get the correct qemu-kvm version from the rhev repository?</li> </ul> Assuming that redhat doesn't provide the same qemu-kvm in rhev than in el6, what about including qemu-kvm-rhev in the ovirt el6 repository as dreyou did ? Thanks <pre class="moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet(a)abes.fr</a> </pre> </body> </html> --------------080009080202040109020900--

8 13

[Users] hosted-engine deployment doesn't accept legal email address (ovirt-3.4.0-prerelease)
by Giorgio Bersano 16 Feb '14

16 Feb '14

Hi, I am happily testing the hosted engine feature, sorry I was late on the test day but I dare to provide some feedback. To be more clear I prefer to report one item per email. This is related to a really minor issue I think it doesn't deserve a Bugzilla but I'm ready to do it if requested. So, during # hosted-engine --deploy in the step named "--== HOSTED ENGINE CONFIGURATION ==--" we are asked to provide a couple of email addresses but addresses with an hypen before the @ sign (ex. my-name(a)mydomain.com ) aren't allowed and throwns the following: [ ERROR ] Invalid input, please try again As a workaround I used another address but, looking at /usr/share/ovirt-hosted-engine-setup/plugins/ovirt-hosted-engine-setup/ha/ha_notifications.py (ovirt-hosted-engine-setup-1.1.0-0.5.beta2.el6.noarch) I've found that _RE_EMAIL_ADDRESS is using a simplified pattern (hope that gmail doesn't mangles text too much): [a-zA-Z0-9_.+]+ @ [a-z0-9.-]+ even avoiding the intricacy of the whole possibilities (see "Local part" in http://en.wikipedia.org/wiki/Email_address ) I think the following (not tested) could be more appropriate: [a-zA-Z0-9] [a-zA-Z0-9_.+-]+ [a-zA-Z0-9] @ [a-z0-9.-]+ don't know if it really works as I've never programmed in python but I hope you get the idea. Best regards, Giorgio.

2 3

[Users] snapshots not shown in webadmin on 3.3.3
by Juan Pablo Lorier 15 Feb '14

15 Feb '14

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --APdkdNOel5hXd7IdFmx4QMVqj4ptcbmOv Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I've updated to 3.3.3 last week and now I find that the snapshots are not shown in webadmin. I've taken some new ones to see if it was due to the migration, but though they finish correctly, they are not shown in the webadmin tab. Is there a way to list the snapshots other than the webadmin? Regards, --APdkdNOel5hXd7IdFmx4QMVqj4ptcbmOv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+6NIAAoJEC5KDDg2+NMMsasH/0KBMU/6Iep7qSWqcFyY3E5R Teit84O2GHsP/JiDtaBF5W4ZloUg+rkMP9/BzhC6I1PYssA4Lq3iiLXQhnJuTqty 8U+hUvksG4CxywCpNS30/Bmx0Czf/dFnIJK5jYtmG+zyIgih+mVS7BEROZRzlxmf ElHbfJ/0c0l29ODOKBVj+nRzEggjW8Vt/sOasaiY/z8zq1rA9eoTw8/WgM5Jev1n m0Nrbqm8ZkOq4WtYSVhV5pkMAfZ4rL92mCC/h+o1nZYpE1EjytOH9nlsMF/bjgpU GjpFmI/nCmX+hbQ8RGgoSqw/o4o16msAXTppMxcT9k2YpoSiteETjO8QupueElY= =BOYv -----END PGP SIGNATURE----- --APdkdNOel5hXd7IdFmx4QMVqj4ptcbmOv--

4 5