- Users - oVirt List Archives

[Users] SPICE causes migration failure?
by Ted Miller 05 Mar '14

05 Mar '14

I just got my Data Center running again, and am proceeding with some setup & testing. I created a VM (not doing anything useful) I clicked on the "Console" and had a SPICE console up (viewed in Win7). I had it printing the time on the screen once per second (while date;do sleep 1; done). I tried to migrate the VM to another host and got in the GUI: Migration started (VM: web1, Source: s1, Destination: s3, User: admin@internal). Migration failed due to Error: Fatal error during migration (VM: web1, Source: s1, Destination: s3). As I started the migration I happened to think "I wonder how they handle the SPICE console, since I think that is a link from the host to my machine, letting me see the VM's screen." After the failure, I tried shutting down the SPICE console, and found that the migration succeeded. I again opened SPICE and had a migration fail. Closed SPICE, migration failed. I can understand how migrating SPICE is a problem, but, at least could we give the victim of this condition a meaningful error message? I have seen a lot of questions about failed migrations (mostly due to attached CDs), but I have never seen this discussed. If I had not had that particular thought cross my brain at that particular time, I doubt that SPICE would have been where I went looking for a solution. If this is the first time this issue has been raised, I am willing to file a bug. Ted Miller Elkhart, IN, USA

3 3

Re: [Users] oVirt 3.5 planning
by Juan Pablo Lorier 05 Mar '14

05 Mar '14

Hi, I'm kind of out of date at this time, but I'd like to propose something that was meant for 3.4 and I don't know it it made into it; use any nfs share as either a iso or export so you can just copy into the share and then update in some way the db. Also, make export domain able to be shared among dcs as is iso domain, that is an rfe from long time ago and a useful one. Attaching and dettaching domains is both time consuming and boring. Also using tagged and untagged networks on top of the same nic. Everybody does that except for ovirt. I also like to say that tough I have a huge enthusiasm for ovirt's fast evolution, I think that you may need to slow down with adding new features until most of the rfes that have over a year are done, because other way it's kind of disappointing opening a rfe just to see it sleeping too much time. Don't take this wrong, I've been listened and helped by the team everytime I needed and I'm thankful for that. Regards,

2 2

[Users] [ANN] oVirt 3.4.0 Release Candidate is now available
by Sandro Bonazzola 04 Mar '14

04 Mar '14

The oVirt team is pleased to announce that the 3.4.0 Release Candidate is now available for testing. Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release. An oVirt Node iso is already available, unchanged from third beta. You're welcome to join us testing this release candidate in next week test day [2] scheduled for 2014-03-06! [1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 7

[Users] Host requirements for 3.4 compatibility
by Darren Evenson 04 Mar '14

04 Mar '14

--_000_95F206E8E9D71348930EC3BF6DA3BFD6490EC02264CLICK03clicki_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have updated my engine to 3.4 rc. I created a new cluster with 3.4 compatibility version, and then I moved a = host I had in maintenance mode to the new cluster. When I activate it, I get the error "Host kvmhost2 is compatible with versi= ons (3.0,3.1,3.2,3.3) and cannot join Cluster Cluster_new which is set to v= ersion 3.4." My host was Fedora 20 with the latest updates: Kernel Version: 3.13.4 - 200.fc20.x86_64 KVM Version: 1.6.1 - 3.fc20 LIBVIRT Version: libvirt-1.1.3.3-5.fc20 VDSM Version: vdsm-4.13.3-3.fc20 So I enabled fedora-virt-preview and updated, but I still get the same erro= r, even now with libvirt 1.2.1: Kernel Version: 3.13.4 - 200.fc20.x86_64 KVM Version: 1.7.0 - 5.fc20 LIBVIRT Version: libvirt-1.2.1-3.fc20 VDSM Version: vdsm-4.13.3-3.fc20 What am I missing? - Darren --_000_95F206E8E9D71348930EC3BF6DA3BFD6490EC02264CLICK03clicki_ 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=3DContent-Type content= =3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros= oft Word 14 (filtered medium)"><style></style></head><body lang=3DEN-US link=3D"#0563C1= " vlink=3D"#954F72"><div class=3DWordSection1>I have u= pdated my engine to 3.4 rc.<o:p></o:p><o:p> <= /o:p>I created a new cluster with 3.4 compatibilit= y version, and then I moved a host I had in maintenance mode to the new clu= ster.<o:p></o:p><o:p> </o:p>When I activate it, I get the error “Host kvmhost2 is compati= ble with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Cluster_new whi= ch is set to version 3.4.”<o:p></o:p><o:p>&n= bsp;</o:p>My host was Fedora 20 with the latest up= dates:<o:p></o:p><o:p> </o:p>Kernel Version: 3.13.4 - 200.fc20.x86_64<o:p></o:p>KVM Version: 1.6.1 - 3.fc20<o:p></o:p>LI= BVIRT Version: libvirt-1.1.3.3-5.fc20<o:p></o:p>VD= SM Version: vdsm-4.13.3-3.fc20<o:p></o:p><o:p>&nbs= p;</o:p>So I enabled fedora-virt-preview and updat= ed, but I still get the same error, even now with libvirt 1.2.1:<o:p></o:p>= <o:p> </o:p>Kernel V= ersion: 3.13.4 - 200.fc20.x86_64<o:p></o:p>KVM Ver= sion: 1.7.0 - 5.fc20<o:p></o:p>LIBVIRT Version: li= bvirt-1.2.1-3.fc20<o:p></o:p>VDSM Version: vdsm-4.= 13.3-3.fc20<o:p></o:p><o:p> </o:p>What am I missing?<o:p></o:p><o:p>&n= bsp;</o:p>- Darren<o:p></o:p><o:p> </o:p></div></body></html>= --_000_95F206E8E9D71348930EC3BF6DA3BFD6490EC02264CLICK03clicki_--

3 6

[Users] [QE] oVirt 3.4.0 status
by Sandro Bonazzola 04 Mar '14

04 Mar '14

Hi, oVirt 3.4.0 RC has been released and is currently on QA. While we're preparing for this week Test Day on 2014-03-06 a few blockers have been opened. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary infra 1070742 POST [database] support postgres user length within schema version infra 1071536 POST Notifier doesn't send any notifications via email integration 1067058 POST [database] old psycopg2 does not accept unicode string as port name integration 1069193 POST Release maven artifacts with correct version numbers integration 1072307 POST remote database cannot be used virt 1069201 ASSIGNED [REST]: Missing domain field on VM\Template object. virt 1071997 POST VM is not locked on run once All remaining bugs have been re-targeted to 3.4.1. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-03-11 09:00 UTC if you want them to be included in 3.4.0 GA. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs and fix them as soon as possible - Please fill release notes, the page has been created here [2] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-19 Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-03-06! Thanks to all people already testing 3.4.0 RC! [1] https://bugzilla.redhat.com/1024889 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Recommended way to disconnect and remove iSCSI direct LUNs
by Boyan Tabakov 04 Mar '14

04 Mar '14

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VQiJjAHh4OqnW9GHojIg6s1LSghwPBraw Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, I have ovirt 3.3.2 running with FC19 nodes. I have several virtual machines that use directly attached iSCSI LUNs. Discovering, attaching and using new LUNs works without issues (vdsm needed some patching to work with Dell Equallogic, as described here https://sites.google.com/a/keele.ac.uk/partlycloudy/ovirt, but that's a separate issue). Also live migration works well between hosts and the LUNs get properly attached to the migration target host. However, I don't see any way to disconnect/remove LUNs that are no longer needed (e.g. VM is removed). What is the recommended way to remove old LUNs, so that the underlying iSCSI sessions are disconnected? Especially if a VM has been migrated between hosts, it leaves the LUNs connected on multiple nodes. Thank you in advance! Best regards, Boyan Tabakov --VQiJjAHh4OqnW9GHojIg6s1LSghwPBraw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMN4OIACgkQXOXFG4fgV77UqgCg2dNkHFiaLHkieT/Cao407JpH 7SMAoIoyTcqIgz+mzjTGW+SfbKs7vnEp =wBiV -----END PGP SIGNATURE----- --VQiJjAHh4OqnW9GHojIg6s1LSghwPBraw--

2 2

[Users] [QE] oVirt 3.3.5 status
by Sandro Bonazzola 04 Mar '14

04 Mar '14

Hi, now that 3.3.4 has been released, it's time to look at 3.3.5. Here is the tentative timeline: General availability: 2014-04-09 RC Build: 2014-04-02 Nightly builds are available enabling the oVirt 3.3 snapshots repositories: # yum-config-manager --enable ovirt-3.3-snapshot # yum-config-manager --enable ovirt-3.3-snapshot-static As you can see there won't be any beta release before RC for 3.3.z and the same will be for 3.4.z. Now we've nightly builds also for stable branches so you can test them whenever you want to. If you're going to test it, please add yourself as tester on [3] Note to maintainers: * For Release candidate builds, we'll send to all maintainers a reminder the week before the build on Thursday morning (UTC timezone). Packages that won't be ready before the announced compose time won't be added to the release candidate. Please remember to build your packages the day before repository composition if you want it in. * Release notes must be filled [1] * A tracker bug has been created [2] and shows 1 bug blocking the release: Whiteboard Bug ID Summary virt 1071997 VM is not locked on run once * Please add bugs to the tracker if you think that 3.3.5 should not be released without them fixed. [1] http://www.ovirt.org/OVirt_3.3.5_release_notes [2] http://bugzilla.redhat.com/1071867 [3] http://www.ovirt.org/Testing/oVirt_3.3.5_testing Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] [ANN] oVirt 3.3.4 release
by Sandro Bonazzola 04 Mar '14

04 Mar '14

The oVirt development team is pleased to announce the general availability of oVirt 3.3.4 as of March 4th 2014. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The existing repository ovirt-stable has been updated for delivering this release without the need of enabling any other repository. A new oVirt Node build is also available [2]. [1] http://www.ovirt.org/OVirt_3.3.4_release_notes [2] http://resources.ovirt.org/releases/3.3.4/iso/ovirt-node-iso-3.0.4-1.0.2014… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Using ovirt-node with virt-mananager
by Andy Michielsen 04 Mar '14

04 Mar '14

Hello, How do I connect to an ovirt nodr with virt manager. Kind regards.

2 1

[Users] Setting up an ovirt-node
by Andy Michielsen 04 Mar '14

04 Mar '14

Hello, I did a clean install of a ovirt-node with the iso provided from ovirt. Everything went fine until I logged on with the admin user and configured the ovirt-engines address. Now I don't have any network connection any more. I have 2 nic's available and defined only the first one with a static IP. When I check the network settings in the admin menu it tells me I have serveral bond devices. If I log on with a root user it states that under /etc/sysconfig/network_scripts that there is a ifcfg_em1, ifcfg_ovirtmgmt and a ifcfg_brem1. The two last devices use the same static ip that I defined on the ifcfg_em1. How can I get my network back up and runnig as I will need this to connect to the engine which is running on an other server. Kind regards.

3 3

[Users] Which ovirt-node version to use
by Andy Michielsen 04 Mar '14

04 Mar '14

Hello, Which ovirt-node iso should I use to install and use with the ovirt-engine 3.3 Kind regards.

2 1

[Users] Which iso to use when installing an ovirt-node
by Andy Michielsen 04 Mar '14

04 Mar '14

Hello, Which iso should I use to install an ovirt-node ? What the difference between the el and fc versions. (I'm installing the engine on a centos 6.5 minimal server.) Which version should I use. Kind regards.

2 1

Re: [Users] SPICE causes migration failure?
by Dafna Ron 04 Mar '14

04 Mar '14

Thanks Ted, Please send logs to the user's list since others may help if I am off line Thanks, Dafna On 03/03/2014 11:48 PM, Ted Miller wrote: > Dafna, I will get the logs to you when I get a chance. I have an > intern to keep busy this week, and that gets higher priority than > oVirt (unfortunately). Ted Miller > > On 3/3/2014 12:26 PM, Dafna Ron wrote: >> I don't see a reason why open monitor will fail migration - at most, >> if there is a problem I would close the spice session on src and >> restarted it at the dst. >> can you please attach vdsm/libvirt/qemu logs from both hosts and >> engine logs so that we can see the migration failure reason? >> >> Thanks, >> Dafna >> >> >> >> On 03/03/2014 05:16 PM, Ted Miller wrote: >>> I just got my Data Center running again, and am proceeding with some >>> setup & testing. >>> >>> I created a VM (not doing anything useful) >>> I clicked on the "Console" and had a SPICE console up (viewed in Win7). >>> I had it printing the time on the screen once per second (while >>> date;do sleep 1; done). >>> I tried to migrate the VM to another host and got in the GUI: >>> >>> Migration started (VM: web1, Source: s1, Destination: s3, User: >>> admin@internal). >>> >>> Migration failed due to Error: Fatal error during migration (VM: >>> web1, Source: s1, Destination: s3). >>> >>> As I started the migration I happened to think "I wonder how they >>> handle the SPICE console, since I think that is a link from the host >>> to my machine, letting me see the VM's screen." >>> >>> After the failure, I tried shutting down the SPICE console, and >>> found that the migration succeeded. I again opened SPICE and had a >>> migration fail. Closed SPICE, migration failed. >>> >>> I can understand how migrating SPICE is a problem, but, at least >>> could we give the victim of this condition a meaningful error >>> message? I have seen a lot of questions about failed migrations >>> (mostly due to attached CDs), but I have never seen this discussed. >>> If I had not had that particular thought cross my brain at that >>> particular time, I doubt that SPICE would have been where I went >>> looking for a solution. >>> >>> If this is the first time this issue has been raised, I am willing >>> to file a bug. >>> >>> Ted Miller >>> Elkhart, IN, USA >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >> >> > -- Dafna Ron

1 0

[Users] oVirt February 2014 Updates
by Itamar Heim 04 Mar '14

04 Mar '14

1. Releases - oVirt 3.3.3 was released early in the month: http://www.ovirt.org/OVirt_3.3.3_release_notes - oVirt 3.3.4 about to release. http://www.ovirt.org/OVirt_3.3.4_release_notes - oVirt 3.4.0 about to release! 2. Events - Leonardo Vaz is organizing ovirt attendance at FISL15, the largest FOSS conference in LATAM which will happen from 7th to 10th of May in Porto Alegre, Brazil: http://softwarelivre.org/fisl15 - Allon Mureinik gave a presentation on DR with oVirt at devconf.cz http://www.slideshare.net/AllonMureinik/dev-conf-ovirt-dr - oVirt workshop in korea slides (korean) http://www.slideshare.net/rogan/20140208-ovirtkorea-01 https://www.facebook.com/groups/ovirt.korea - Rogan also presented oVirt integration with OpenStack in OpenStack day in Korea http://alturl.com/m3jnx - Pat Pierson posted on basic network setup http://izen.ghostpeppersrus.com/setting-up-networks/ - Fosdem 2014 sessions (slides and videos) are at: http://www.ovirt.org/FOSDEM_2014 - and some at Infrastructure.Next Ghent the week after forsdem. 3. oVirt Activity (software) - oVirt Jenkins plugin by Dustin Kut Moy Cheung to control VM slaves managed by ovirt/RHEV https://github.com/thescouser89/ovirt-slaves-plugin - Opaque oVirt/RHEV/Proxmox client and source code released https://play.google.com/store/apps/details?id=com.undatech.opaque - great to see the NUMA push from HP: http://www.ovirt.org/Features/NUMA_and_Virtual_NUMA http://www.ovirt.org/Features/Detailed_NUMA_and_Virtual_NUMA 4. oVirt Activity (blogs, preso's) - oVirt's has been accepted as a mentoring project for the Google Summer of Code 2014. - Oved Ourfali posted on "Importing Glance images as oVirt templates" http://alturl.com/h7xid - v2v had seen many active discussions. here's a post by Jon Archer on how to Import regular kvm image to oVirt or RHEV http://jonarcher.info/2014/02/import-regular-kvm-image-ovirt-rhev/ - great reviews on amazon.com for "Getting Started with oVirt 3.3" http://alturl.com/5rk2p - oVirt Deep Dive 3.3 slides (Chinese) http://www.slideshare.net/mobile/johnwoolee/ovirt-deep-dive# - oVirt intro video (russian) http://alturl.com/it546 - how to install oVirt 3.3 on CentOS 6.5 http://www.youtube.com/watch?v=5i5ilSKsmbo 5. Related - NetApp GA'd their Virtual Storage Console for RHEV, which is implemented as an oVirt UI plugin (and then some) http://captainkvm.com/2014/02/vsc-for-rhev-is-ga-today/#more-660

3 2

Re: [Users] method "glusterHostsList" is not supported
by Itamar Heim 04 Mar '14

04 Mar '14

On 03/04/2014 11:15 AM, René Koch wrote: > On 03/04/2014 09:40 AM, Itamar Heim wrote: >> On 03/04/2014 10:16 AM, René Koch wrote: >>> On 03/04/2014 05:14 AM, Sahina Bose wrote: >>>> >>>> On 03/04/2014 01:59 AM, Itamar Heim wrote: >>>>> On 03/03/2014 07:26 PM, René Koch wrote: >>>>>> Hi list, >>>>>> >>>>>> My hosted engine is running again, so I want to start a new thread >>>>>> for >>>>>> another issue with my setup. >>>>>> >>>>>> I have a GlusterFS storage domain, which can be mounted from CLI >>>>>> without >>>>>> problems. oVirt is 3.4 from ovirt-3.4.0-prerelease repository >>>>>> running on >>>>>> CentOS 6.5 with latest updates (both OS and oVirt). >>>>>> >>>>>> Both hosts, which act as hypervisors and GlusterFS nodes are in state >>>>>> "Non Operational" in oVirt because "Gluster command [Non interactive >>>>>> user] failed on server ovirt-host02.dmz.linuxland.at." >>>>>> >>>>>> In engine.log I see the entry "glusterHostList is not supported" >>>>>> (attached are the log entries when activating one of the hosts): >>>>>> >>>>>> 2014-03-03 18:17:11,764 ERROR >>>>>> [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] >>>>>> >>>>>> (org.ovirt.thread.pool-6-thread-21) [6eee3cbd] Command >>>>>> GlusterServersListVDSCommand(HostName = >>>>>> ovirt-host02.dmz.linuxland.at, >>>>>> HostId = dd399eeb-f623-457a-9986-a7efc69010b2) execution failed. >>>>>> Exception: VDSNetworkException: org.apache.xmlrpc.XmlRpcException: >>>>>> <type >>>>>> 'exceptions.Exception'>:method "glusterHostsList" is not supported >>>>>> >>>>>> Can you give me a hint what this means and how I can activate my >>>>>> hosts >>>>>> and storage again? >>>>>> Thanks a lot! >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list >>>>>> Users(a)ovirt.org >>>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>>> >>>>> >>>>> sahina ? >>>> >>>> Do you have vdsm-gluster on the node? >>> >>> No, I didn't had it on (both) nodes. >>> >>> After installing vdsm-gluster the storage works fine again. Thanks a >>> lot! >>> >>> But there's one strange thing. According to oVirt logs and yum.log >>> GlusterFS storage worked fine until yesterdays "yum update", where the >>> following packages where updated: >>> >>> Mar 03 10:01:09 Updated: ovirt-hosted-engine-ha-1.1.0-1.el6.noarch >>> Mar 03 10:01:10 Updated: otopi-1.2.0-0.5.rc.el6.noarch >>> Mar 03 10:01:11 Updated: ovirt-engine-sdk-python-3.4.0.6-1.el6.noarch >>> Mar 03 10:01:12 Updated: ovirt-hosted-engine-setup-1.1.0-1.el6.noarch >>> Mar 03 10:01:13 Updated: libtiff-3.9.4-10.el6_5.x86_64 >>> >>> According to yum.log vdsm-gluster was never installed on these hosts, >>> but storage did work. >>> >>> Shouldn't vdsm-gluster be a requirement for hosts and therefor be >>> installed during host setup? >>> >>> Do you have any clue why it storage did work until the update of these >>> packages? >> >> vdsm-gluster is to manage gluster storage, not consume gluster storage. >> did you enable the gluster mode post installing the hosts? >> (if you enabled it before installing them, or re-install[1] post >> enabling gluster mode, it should have deployed vdsm-gluster as well) >> >> [1] after moving hos to maintenance. > > Yes, I did it after installing the hosts. > > Would it be possible to add a check before activating this option? > > I'm thinking of the following: > - Edit Cluster > - Enable Gluster Service > - OK checks if all hosts in the cluster have vdsm-gluster installed - if > not an error message occurs that this package is required in order to > enable the gluster service. makes sense - please open a bug to track. check would probably warn if unreachable hosts exists to warn user.

2 1

Re: [Users] method "glusterHostsList" is not supported
by Itamar Heim 04 Mar '14

04 Mar '14

On 03/04/2014 10:16 AM, René Koch wrote: > On 03/04/2014 05:14 AM, Sahina Bose wrote: >> >> On 03/04/2014 01:59 AM, Itamar Heim wrote: >>> On 03/03/2014 07:26 PM, René Koch wrote: >>>> Hi list, >>>> >>>> My hosted engine is running again, so I want to start a new thread for >>>> another issue with my setup. >>>> >>>> I have a GlusterFS storage domain, which can be mounted from CLI >>>> without >>>> problems. oVirt is 3.4 from ovirt-3.4.0-prerelease repository >>>> running on >>>> CentOS 6.5 with latest updates (both OS and oVirt). >>>> >>>> Both hosts, which act as hypervisors and GlusterFS nodes are in state >>>> "Non Operational" in oVirt because "Gluster command [Non interactive >>>> user] failed on server ovirt-host02.dmz.linuxland.at." >>>> >>>> In engine.log I see the entry "glusterHostList is not supported" >>>> (attached are the log entries when activating one of the hosts): >>>> >>>> 2014-03-03 18:17:11,764 ERROR >>>> [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] >>>> (org.ovirt.thread.pool-6-thread-21) [6eee3cbd] Command >>>> GlusterServersListVDSCommand(HostName = ovirt-host02.dmz.linuxland.at, >>>> HostId = dd399eeb-f623-457a-9986-a7efc69010b2) execution failed. >>>> Exception: VDSNetworkException: org.apache.xmlrpc.XmlRpcException: >>>> <type >>>> 'exceptions.Exception'>:method "glusterHostsList" is not supported >>>> >>>> Can you give me a hint what this means and how I can activate my hosts >>>> and storage again? >>>> Thanks a lot! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>> >>> sahina ? >> >> Do you have vdsm-gluster on the node? > > No, I didn't had it on (both) nodes. > > After installing vdsm-gluster the storage works fine again. Thanks a lot! > > But there's one strange thing. According to oVirt logs and yum.log > GlusterFS storage worked fine until yesterdays "yum update", where the > following packages where updated: > > Mar 03 10:01:09 Updated: ovirt-hosted-engine-ha-1.1.0-1.el6.noarch > Mar 03 10:01:10 Updated: otopi-1.2.0-0.5.rc.el6.noarch > Mar 03 10:01:11 Updated: ovirt-engine-sdk-python-3.4.0.6-1.el6.noarch > Mar 03 10:01:12 Updated: ovirt-hosted-engine-setup-1.1.0-1.el6.noarch > Mar 03 10:01:13 Updated: libtiff-3.9.4-10.el6_5.x86_64 > > According to yum.log vdsm-gluster was never installed on these hosts, > but storage did work. > > Shouldn't vdsm-gluster be a requirement for hosts and therefor be > installed during host setup? > > Do you have any clue why it storage did work until the update of these > packages? vdsm-gluster is to manage gluster storage, not consume gluster storage. did you enable the gluster mode post installing the hosts? (if you enabled it before installing them, or re-install[1] post enabling gluster mode, it should have deployed vdsm-gluster as well) [1] after moving hos to maintenance.

2 1

Re: [Users] method "glusterHostsList" is not supported
by Sahina Bose 04 Mar '14

04 Mar '14

On 03/04/2014 01:46 PM, René Koch wrote: > On 03/04/2014 05:14 AM, Sahina Bose wrote: >> >> On 03/04/2014 01:59 AM, Itamar Heim wrote: >>> On 03/03/2014 07:26 PM, René Koch wrote: >>>> Hi list, >>>> >>>> My hosted engine is running again, so I want to start a new thread for >>>> another issue with my setup. >>>> >>>> I have a GlusterFS storage domain, which can be mounted from CLI >>>> without >>>> problems. oVirt is 3.4 from ovirt-3.4.0-prerelease repository >>>> running on >>>> CentOS 6.5 with latest updates (both OS and oVirt). >>>> >>>> Both hosts, which act as hypervisors and GlusterFS nodes are in state >>>> "Non Operational" in oVirt because "Gluster command [Non interactive >>>> user] failed on server ovirt-host02.dmz.linuxland.at." >>>> >>>> In engine.log I see the entry "glusterHostList is not supported" >>>> (attached are the log entries when activating one of the hosts): >>>> >>>> 2014-03-03 18:17:11,764 ERROR >>>> [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] >>>> (org.ovirt.thread.pool-6-thread-21) [6eee3cbd] Command >>>> GlusterServersListVDSCommand(HostName = ovirt-host02.dmz.linuxland.at, >>>> HostId = dd399eeb-f623-457a-9986-a7efc69010b2) execution failed. >>>> Exception: VDSNetworkException: org.apache.xmlrpc.XmlRpcException: >>>> <type >>>> 'exceptions.Exception'>:method "glusterHostsList" is not supported >>>> >>>> Can you give me a hint what this means and how I can activate my hosts >>>> and storage again? >>>> Thanks a lot! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>> >>> sahina ? >> >> Do you have vdsm-gluster on the node? > > No, I didn't had it on (both) nodes. > > After installing vdsm-gluster the storage works fine again. Thanks a lot! > > But there's one strange thing. According to oVirt logs and yum.log > GlusterFS storage worked fine until yesterdays "yum update", where the > following packages where updated: > > Mar 03 10:01:09 Updated: ovirt-hosted-engine-ha-1.1.0-1.el6.noarch > Mar 03 10:01:10 Updated: otopi-1.2.0-0.5.rc.el6.noarch > Mar 03 10:01:11 Updated: ovirt-engine-sdk-python-3.4.0.6-1.el6.noarch > Mar 03 10:01:12 Updated: ovirt-hosted-engine-setup-1.1.0-1.el6.noarch > Mar 03 10:01:13 Updated: libtiff-3.9.4-10.el6_5.x86_64 > > According to yum.log vdsm-gluster was never installed on these hosts, > but storage did work. > > Shouldn't vdsm-gluster be a requirement for hosts and therefor be > installed during host setup? > > Do you have any clue why it storage did work until the update of these > packages? The host moving to Non-Operational state with error "Gluster command failed..." is dependent on whether "Enable gluster service" is checked on your cluster. This check indicates that you also want to manage gluster storage provisioning on the nodes. A recent change now checks that vdsm-gluster support is available for such clusters. That's probably why you are seeing this error after update. > > > Regards, > René >

2 1

[Users] method "glusterHostsList" is not supported
by René Koch 04 Mar '14

04 Mar '14

Hi list, My hosted engine is running again, so I want to start a new thread for another issue with my setup. I have a GlusterFS storage domain, which can be mounted from CLI without problems. oVirt is 3.4 from ovirt-3.4.0-prerelease repository running on CentOS 6.5 with latest updates (both OS and oVirt). Both hosts, which act as hypervisors and GlusterFS nodes are in state "Non Operational" in oVirt because "Gluster command [Non interactive user] failed on server ovirt-host02.dmz.linuxland.at." In engine.log I see the entry "glusterHostList is not supported" (attached are the log entries when activating one of the hosts): 2014-03-03 18:17:11,764 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (org.ovirt.thread.pool-6-thread-21) [6eee3cbd] Command GlusterServersListVDSCommand(HostName = ovirt-host02.dmz.linuxland.at, HostId = dd399eeb-f623-457a-9986-a7efc69010b2) execution failed. Exception: VDSNetworkException: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.Exception'>:method "glusterHostsList" is not supported Can you give me a hint what this means and how I can activate my hosts and storage again? Thanks a lot! -- Best Regards René Koch Senior Solution Architect ============================================ LIS-Linuxland GmbH Brünner Straße 163, A-1210 Vienna Phone: +43 1 236 91 60 Mobile: +43 660 / 512 21 31 E-Mail: rkoch(a)linuxland.at ============================================

3 3

[Users] Creating Logical Network issue - API
by Tejesh M 04 Mar '14

04 Mar '14

Hi , I'm trying to create Logical Network and assign it to cluster & want to bond this to one of the Network Interface on Host. so that i can isolate my VM from other networks. The issue is even if i set Cluster while creating Logical Network, it is not setting the cluster. In Web Admin it is in unset state. Also, let me know how do i bind this Logical network on Host Interface. *Java code:* Network nw1=new Network(); VLAN vlan = new VLAN(); vlan.setId(2000); nw1.setVlan(vlan); IP ip = new IP(); ip.setAddress("192.168.1.151"); ip.setGateway("192.168.1.1"); ip.setNetmask("255.255.255.0"); nw1.setIp(ip); nw1.setName("apiNetwork"); nw1.setDataCenter(api.getDataCenters().get("testDC")); nw1.setCluster(api.getClusters().get("testCluster")); org.ovirt.engine.sdk.decorators.Network nw2 = api.getNetworks().add(nw1); -- Thanks & Regards Tejesh

2 15

[Users] help requested
by aditya mamidwar 03 Mar '14

03 Mar '14

hey, i want to study how ovirt implements the ISCSI protocol for disk access in SANs, i want to study the source code files. from where can i get them? am thinking of implementing the aoe protocol. also can i get help on how such plugins are made for ovirt, which files need to be changed, and procedure to test the plugin by building the engine. -- -Aditya Mamidwar

3 2

[Users] hosted engine setup (network)
by René Koch 03 Mar '14

03 Mar '14

Hi, During hosted engine setup I faced issues with network configuration on my CentOS 6.5 hosts: My network setup was the following which doesn't work with hosted engine setup: - eth0.200 (VLAN tag 200) should become ovirtmgmt interface - GATEWAY is in /etc/sysconfig/network and not in ifcfg-eth0.200 The following errors occured: 014-02-25 15:42:31 INFO otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:189 Configuring the management bridge 2014-02-25 15:42:31 DEBUG otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:198 getVdsCaps for eth0: {'addr': '', 'cfg': {'DEVICE': 'eth0', 'PEERDNS': 'no', 'NM_CONTROLLED': 'no', 'BOOTPROTO': 'none', 'HWADDR': '00:25:9 0:75:87:C2', 'ONBOOT': 'yes'}, 'ipv6addrs': ['fe80::225:90ff:fe75:87c2/64'], 'mtu': '1500', 'netmask': '', 'hwaddr': '00:25:90:75:87:c2', 'speed': 1000} 2014-02-25 15:42:31 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py", line 231, in _misc 'gateway=%s' % caps['cfg']['GATEWAY'], KeyError: 'GATEWAY' This can be solved by setting GATEWAY in ifcfg-eth* file instead of /etc/sysconfig/network Next, VLAN tagged interfaces don't work: 2014-02-25 15:35:20 INFO otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:189 Configuring the management bridge 2014-02-25 15:35:20 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py", line 194, in _misc ].s.getVdsCapabilities()['info']['nics'][nics] KeyError: 'eth0.200' So I had to do the following: - Set switch port to untagged for this VLAN - Configure eth0 instead of eth0.200 - Run hosted engine setup - Configure VLAN for ovirtmgmt in oVirt (which surprisingly worked for an active interface) - Configure VLAN tagging on hosts - Reconfigure switch ports - Sync networks in oVirt network setup tab As this was a real pain to do I would love to see support for VLAN tagging in hosted engine setup :) Shall I open bug reports for these 2 issues or are they already known? -- Best Regards René Koch Senior Solution Architect ============================================ LIS-Linuxland GmbH Brünner Straße 163, A-1210 Vienna Phone: +43 1 236 91 60 Mobile: +43 660 / 512 21 31 E-Mail: rkoch(a)linuxland.at ============================================

2 2

Re: [Users] hosted engine issues
by Martin Sivak 03 Mar '14

03 Mar '14

The agent is required. In fact it contains all the logic. -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ ----- Original Message ----- > On 03/03/2014 02:05 PM, Martin Sivak wrote: > > Hi René, > > > >> # python --version > >> Python 2.6.6 > > > > Then I guess the traceback is my fault... > > > > See http://gerrit.ovirt.org/#/c/25269/ for the fix. I will try to get it > > into the soonest release possible. > > > Thanks. Do I have to patch the files manually or is ovirt-ha-agent not > strictly required for hosted engine? Some features like restarting > engine on 2nd node want work if ovirt-ha-agent isn't working, I guess. > > > > >> I can't see a full filesystem here: > >> > > > > Me neither. Is everything Read-Write? Read-Only FS might report no space > > left as well in some cases. Other than that, I do not know. > > No, I can write to all disks. > Btw, the same error message occurs on both nodes... > > > Regards, > René > > > > > > Regards > > -- > > Martin Sivák > > msivak(a)redhat.com > > Red Hat Czech > > RHEV-M SLA / Brno, CZ > > > > ----- Original Message ----- > >> On 03/03/2014 12:05 PM, Martin Sivak wrote: > >>> Hi René, > >>> > >>> thanks for the report. > >>> > >>>>> TypeError: super() argument 1 must be type, not classobj > >>> What Python version are you using? > >> > >> # python --version > >> Python 2.6.6 > >> > >>> > >>> You can debug a crash of this version of ha-agent using: > >>> > >>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent --no-daemon --pdb > >> > >> This gives me the same information as in vdsm.log > >> > >>> > >>> But this exception is trying to tell you that > >>> FSMLoggerAdapter(logging.LoggerAdapter) does not have object in the > >>> ancestor list. And that is very weird. > >>> > >>> It can be related to the disk space issues. > >>> > >>>>> libvirtError: Failed to acquire lock: No space left on device > >>> > >>> Check the free space on all your devices, including /tmp and /var. Or > >>> post > >>> the output of "df -h" command here > >> > >> I can't see a full filesystem here: > >> > >> # df -h > >> Filesystem Size Used Avail Use% Mounted on > >> /dev/mapper/vg0-lv_root 5.0G 1.1G 3.6G 24% / > >> tmpfs 16G 0 16G 0% /dev/shm > >> /dev/sda1 243M 45M 185M 20% /boot > >> /dev/mapper/vg0-lv_data 281G 21G 261G 8% /data > >> /dev/mapper/vg0-lv_tmp 2.0G 69M 1.9G 4% /tmp > >> /dev/mapper/vg0-lv_var 5.0G 384M 4.3G 9% /var > >> ovirt-host01:/engine 281G 21G 261G 8% > >> /rhev/data-center/mnt/ovirt-host01:_engine > >> > >> > >> Thanks, > >> René > >> > >> > >>> > >>> Regards > >>> > >>> -- > >>> Martin Sivák > >>> msivak(a)redhat.com > >>> Red Hat Czech > >>> RHEV-M SLA / Brno, CZ > >>> > >>> ----- Original Message ----- > >>>> Il 03/03/2014 11:33, René Koch ha scritto: > >>>>> Hi, > >>>>> > >>>>> I have some issues with hosted engine (oVirt 3.4 prerelease repo on > >>>>> CentOS > >>>>> 6.5). > >>>>> My setups is the following: > >>>>> 2 hosts (will be 4 in the future) with 4 GlusterFS shares: > >>>>> - engine (for hosted engine) > >>>>> - iso (for ISO domain) > >>>>> - ovirt (oVirt storage domain) > >>>>> > >>>>> I had a split-brain situation today (after rebooting both nodes) on > >>>>> hosted-engine.lockspace file on engine GlusterFS volume which I > >>>>> resolved. > >>>> > >>>> How did you solved it? By switching to NFS only? > >>>> > >>>> > >>>>> hosted engine used engine share via NFS (TCP) as glusterfs isn't > >>>>> supported > >>>>> for oVirt hosted engine, yet. I'll switch to GlusterFS as soon as oVirt > >>>>> will support it (I hope this will be soon as RHEV 3.3 is already > >>>>> supporting > >>>>> GlusterFS for hosted engine). > >>>>> > >>>>> > >>>>> First of all ovirt-ha-agent fails to start on both nodes: > >>>>> > >>>>> # service ovirt-ha-agent start > >>>>> Starting ovirt-ha-agent: [ OK ] > >>>>> # service ovirt-ha-agent status > >>>>> ovirt-ha-agent dead but subsys locked > >>>>> > >>>>> > >>>>> MainThread::INFO::2014-03-03 > >>>>> 11:20:39,539::agent::52::ovirt_hosted_engine_ha.agent.agent.Agent::(run) > >>>>> ovirt-hosted-engine-ha agent 1.1.0 started > >>>>> MainThread::INFO::2014-03-03 > >>>>> 11:20:39,590::hosted_engine::223::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname) > >>>>> Found > >>>>> certificate common name: 10.0.200.101 > >>>>> MainThread::CRITICAL::2014-03-03 > >>>>> 11:20:39,590::agent::103::ovirt_hosted_engine_ha.agent.agent.Agent::(run) > >>>>> Could not start ha-agent > >>>>> Traceback (most recent call last): > >>>>> File > >>>>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", > >>>>> line 97, in run > >>>>> self._run_agent() > >>>>> File > >>>>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", > >>>>> line 154, in _run_agent > >>>>> hosted_engine.HostedEngine(self.shutdown_requested).start_monitoring() > >>>>> File > >>>>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", > >>>>> line 152, in __init__ > >>>>> "STOP_VM": self._stop_engine_vm > >>>>> File > >>>>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/state_machine.py", > >>>>> line 56, in __init__ > >>>>> logger, actions) > >>>>> File > >>>>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py", > >>>>> line 93, in __init__ > >>>>> self._logger = FSMLoggerAdapter(logger, self) > >>>>> File > >>>>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py", > >>>>> line 16, in __init__ > >>>>> super(FSMLoggerAdapter, self).__init__(logger, None) > >>>>> TypeError: super() argument 1 must be type, not classobj > >>>>> > >>>>> > >>>>> > >>>>> If I want to start my hosted engine, I receive the following error in > >>>>> vdsm > >>>>> logs, which makes absolutly no sense to me, as there is plenty of disk > >>>>> space available: > >>>>> > >>>>> Thread-62::DEBUG::2014-03-03 > >>>>> 11:24:46,282::libvirtconnection::124::root::(wrapper) Unknown > >>>>> libvirterror: ecode: 38 edom: 42 level: 2 message: Failed > >>>>> to acquire lock: No space left on device > >>>> > >>>> seems like a vdsm failure in starting monitor the hosted engine storage > >>>> domain. > >>>> Can you attach vdsm logs? > >>>> > >>>> > >>>> > >>>>> Thread-62::DEBUG::2014-03-03 > >>>>> 11:24:46,282::vm::2252::vm.Vm::(_startUnderlyingVm) > >>>>> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::_ongoingCreations released > >>>>> Thread-62::ERROR::2014-03-03 > >>>>> 11:24:46,283::vm::2278::vm.Vm::(_startUnderlyingVm) > >>>>> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::The vm start process > >>>>> failed > >>>>> Traceback (most recent call last): > >>>>> File "/usr/share/vdsm/vm.py", line 2238, in _startUnderlyingVm > >>>>> self._run() > >>>>> File "/usr/share/vdsm/vm.py", line 3159, in _run > >>>>> self._connection.createXML(domxml, flags), > >>>>> File > >>>>> "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", > >>>>> line > >>>>> 92, in wrapper > >>>>> ret = f(*args, **kwargs) > >>>>> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2665, in > >>>>> createXML > >>>>> if ret is None:raise libvirtError('virDomainCreateXML() failed', > >>>>> conn=self) > >>>>> libvirtError: Failed to acquire lock: No space left on device > >>>>> Thread-62::DEBUG::2014-03-03 > >>>>> 11:24:46,286::vm::2720::vm.Vm::(setDownStatus) > >>>>> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::Changed state to Down: > >>>>> Failed > >>>>> to acquire lock: No space left on device > >>>>> > >>>>> # df -h | grep engine > >>>>> ovirt-host01:/engine 281G 21G 261G 8% > >>>>> /rhev/data-center/mnt/ovirt-host01:_engine > >>>>> > >>>>> # sudo -u vdsm dd if=/dev/zero > >>>>> of=/rhev/data-center/mnt/ovirt-host01:_engine/2851af27-8744-445d-9fb1-a0d083c8dc82/images/0e4d270f-2f7e-4b2b-847f-f114a4ba9bdc/test > >>>>> bs=512 count=100 > >>>>> 100+0 records in > >>>>> 100+0 records out > >>>>> 51200 bytes (51 kB) copied, 0.0230566 s, 2.2 MB/s > >>>>> > >>>>> > >>>>> Could you give me some information on how to fix the ovirt-ha-agent and > >>>>> then hosted-engine storage issue? Thanks a lot. > >>>>> > >>>>> Btw, I had some issues during installation which I will explain in > >>>>> separate > >>>>> emails. > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Sandro Bonazzola > >>>> Better technology. Faster innovation. Powered by community > >>>> collaboration. > >>>> See how it works at redhat.com > >>>> > >> >

2 1

Re: [Users] hosted engine issues
by Yedidyah Bar David 03 Mar '14

03 Mar '14

----- Original Message ----- > From: "René Koch" <rkoch(a)linuxland.at> > To: "Yedidyah Bar David" <didi(a)redhat.com>, "Martin Sivak" <msivak(a)redhat.com> > Cc: users(a)ovirt.org > Sent: Monday, March 3, 2014 4:10:51 PM > Subject: Re: [Users] hosted engine issues > > On 03/03/2014 02:13 PM, Yedidyah Bar David wrote: > >> Me neither. Is everything Read-Write? Read-Only FS might report no space > >> left > >> as well in some cases. Other than that, I do not know. > > > > Perhaps some ipc resource? semaphores? > > > > Please check: > > > > ipcs > > > > cat /proc/sys/kernel/sem > > > > I know nothing about libvirt, that's just a wild guess. > > # ipcs > > ------ Shared Memory Segments -------- > key shmid owner perms bytes nattch status > > 0x00000000 0 root 644 80 2 > > 0x00000000 32769 root 644 16384 2 > > 0x00000000 65538 root 644 280 2 > > > ------ Semaphore Arrays -------- > key semid owner perms nsems > 0x00000000 0 root 600 1 > 0x00000000 65537 root 600 1 > 0x000000a7 163842 root 600 1 This means you have 3 semaphore sets, of one semaphore each. > > ------ Message Queues -------- > key msqid owner perms used-bytes messages > Also the rest is moderate usage. > # cat /proc/sys/kernel/sem > 250 32000 32 128 So you are far from the maxima (250 per set, 32000 total, 128 sets). > > > Do you see anything in this output? > I have no clue how to interpret this... See e.g. http://man7.org/linux/man-pages/man5/proc.5.html Is the above on a node? engine? both nodes are similar? If so, that's not the reason for the "no space left on device". If this error is reproducible, you can try to find the process that this happens to (perhaps libvirtd, vdsmd, or the hosted-engine ha daemon) and do: strace -f -o /tmp/trace1 -tt -s 512 -p PID where PID is the pid of that process, then search /tmp/trace1 for 'no space left on device' and see the exact call that failed. -- Didi

2 1

Re: [Users] hosted engine issues
by Martin Sivak 03 Mar '14

03 Mar '14

Hi René, > # python --version > Python 2.6.6 Then I guess the traceback is my fault... See http://gerrit.ovirt.org/#/c/25269/ for the fix. I will try to get it into the soonest release possible. > I can't see a full filesystem here: > Me neither. Is everything Read-Write? Read-Only FS might report no space left as well in some cases. Other than that, I do not know. Regards -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ ----- Original Message ----- > On 03/03/2014 12:05 PM, Martin Sivak wrote: > > Hi René, > > > > thanks for the report. > > > >>> TypeError: super() argument 1 must be type, not classobj > > What Python version are you using? > > # python --version > Python 2.6.6 > > > > > You can debug a crash of this version of ha-agent using: > > > > /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent --no-daemon --pdb > > This gives me the same information as in vdsm.log > > > > > But this exception is trying to tell you that > > FSMLoggerAdapter(logging.LoggerAdapter) does not have object in the > > ancestor list. And that is very weird. > > > > It can be related to the disk space issues. > > > >>> libvirtError: Failed to acquire lock: No space left on device > > > > Check the free space on all your devices, including /tmp and /var. Or post > > the output of "df -h" command here > > I can't see a full filesystem here: > > # df -h > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/vg0-lv_root 5.0G 1.1G 3.6G 24% / > tmpfs 16G 0 16G 0% /dev/shm > /dev/sda1 243M 45M 185M 20% /boot > /dev/mapper/vg0-lv_data 281G 21G 261G 8% /data > /dev/mapper/vg0-lv_tmp 2.0G 69M 1.9G 4% /tmp > /dev/mapper/vg0-lv_var 5.0G 384M 4.3G 9% /var > ovirt-host01:/engine 281G 21G 261G 8% > /rhev/data-center/mnt/ovirt-host01:_engine > > > Thanks, > René > > > > > > Regards > > > > -- > > Martin Sivák > > msivak(a)redhat.com > > Red Hat Czech > > RHEV-M SLA / Brno, CZ > > > > ----- Original Message ----- > >> Il 03/03/2014 11:33, René Koch ha scritto: > >>> Hi, > >>> > >>> I have some issues with hosted engine (oVirt 3.4 prerelease repo on > >>> CentOS > >>> 6.5). > >>> My setups is the following: > >>> 2 hosts (will be 4 in the future) with 4 GlusterFS shares: > >>> - engine (for hosted engine) > >>> - iso (for ISO domain) > >>> - ovirt (oVirt storage domain) > >>> > >>> I had a split-brain situation today (after rebooting both nodes) on > >>> hosted-engine.lockspace file on engine GlusterFS volume which I resolved. > >> > >> How did you solved it? By switching to NFS only? > >> > >> > >>> hosted engine used engine share via NFS (TCP) as glusterfs isn't > >>> supported > >>> for oVirt hosted engine, yet. I'll switch to GlusterFS as soon as oVirt > >>> will support it (I hope this will be soon as RHEV 3.3 is already > >>> supporting > >>> GlusterFS for hosted engine). > >>> > >>> > >>> First of all ovirt-ha-agent fails to start on both nodes: > >>> > >>> # service ovirt-ha-agent start > >>> Starting ovirt-ha-agent: [ OK ] > >>> # service ovirt-ha-agent status > >>> ovirt-ha-agent dead but subsys locked > >>> > >>> > >>> MainThread::INFO::2014-03-03 > >>> 11:20:39,539::agent::52::ovirt_hosted_engine_ha.agent.agent.Agent::(run) > >>> ovirt-hosted-engine-ha agent 1.1.0 started > >>> MainThread::INFO::2014-03-03 > >>> 11:20:39,590::hosted_engine::223::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname) > >>> Found > >>> certificate common name: 10.0.200.101 > >>> MainThread::CRITICAL::2014-03-03 > >>> 11:20:39,590::agent::103::ovirt_hosted_engine_ha.agent.agent.Agent::(run) > >>> Could not start ha-agent > >>> Traceback (most recent call last): > >>> File > >>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", > >>> line 97, in run > >>> self._run_agent() > >>> File > >>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", > >>> line 154, in _run_agent > >>> hosted_engine.HostedEngine(self.shutdown_requested).start_monitoring() > >>> File > >>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", > >>> line 152, in __init__ > >>> "STOP_VM": self._stop_engine_vm > >>> File > >>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/state_machine.py", > >>> line 56, in __init__ > >>> logger, actions) > >>> File > >>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py", > >>> line 93, in __init__ > >>> self._logger = FSMLoggerAdapter(logger, self) > >>> File > >>> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py", > >>> line 16, in __init__ > >>> super(FSMLoggerAdapter, self).__init__(logger, None) > >>> TypeError: super() argument 1 must be type, not classobj > >>> > >>> > >>> > >>> If I want to start my hosted engine, I receive the following error in > >>> vdsm > >>> logs, which makes absolutly no sense to me, as there is plenty of disk > >>> space available: > >>> > >>> Thread-62::DEBUG::2014-03-03 > >>> 11:24:46,282::libvirtconnection::124::root::(wrapper) Unknown > >>> libvirterror: ecode: 38 edom: 42 level: 2 message: Failed > >>> to acquire lock: No space left on device > >> > >> seems like a vdsm failure in starting monitor the hosted engine storage > >> domain. > >> Can you attach vdsm logs? > >> > >> > >> > >>> Thread-62::DEBUG::2014-03-03 > >>> 11:24:46,282::vm::2252::vm.Vm::(_startUnderlyingVm) > >>> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::_ongoingCreations released > >>> Thread-62::ERROR::2014-03-03 > >>> 11:24:46,283::vm::2278::vm.Vm::(_startUnderlyingVm) > >>> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::The vm start process failed > >>> Traceback (most recent call last): > >>> File "/usr/share/vdsm/vm.py", line 2238, in _startUnderlyingVm > >>> self._run() > >>> File "/usr/share/vdsm/vm.py", line 3159, in _run > >>> self._connection.createXML(domxml, flags), > >>> File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", > >>> line > >>> 92, in wrapper > >>> ret = f(*args, **kwargs) > >>> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2665, in > >>> createXML > >>> if ret is None:raise libvirtError('virDomainCreateXML() failed', > >>> conn=self) > >>> libvirtError: Failed to acquire lock: No space left on device > >>> Thread-62::DEBUG::2014-03-03 > >>> 11:24:46,286::vm::2720::vm.Vm::(setDownStatus) > >>> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::Changed state to Down: > >>> Failed > >>> to acquire lock: No space left on device > >>> > >>> # df -h | grep engine > >>> ovirt-host01:/engine 281G 21G 261G 8% > >>> /rhev/data-center/mnt/ovirt-host01:_engine > >>> > >>> # sudo -u vdsm dd if=/dev/zero > >>> of=/rhev/data-center/mnt/ovirt-host01:_engine/2851af27-8744-445d-9fb1-a0d083c8dc82/images/0e4d270f-2f7e-4b2b-847f-f114a4ba9bdc/test > >>> bs=512 count=100 > >>> 100+0 records in > >>> 100+0 records out > >>> 51200 bytes (51 kB) copied, 0.0230566 s, 2.2 MB/s > >>> > >>> > >>> Could you give me some information on how to fix the ovirt-ha-agent and > >>> then hosted-engine storage issue? Thanks a lot. > >>> > >>> Btw, I had some issues during installation which I will explain in > >>> separate > >>> emails. > >>> > >>> > >> > >> > >> -- > >> Sandro Bonazzola > >> Better technology. Faster innovation. Powered by community collaboration. > >> See how it works at redhat.com > >> >

3 3

[Users] Installing ovirt-engine on ovirt-node
by Andy Michielsen 03 Mar '14

03 Mar '14

Hello, Can I use the ovirt-node iso (3.0.4-1.0.201401291204.vdsm33.el6) to install an ovirt-engine on. This way I don't have to worry about installing a centos 6.5 and installing to much. Kind regards.

2 1