- Users - oVirt List Archives

Cannot export FC vms to NFS export
by Fabien CARRE 31 Jul '14

31 Jul '14

Hello, Since I cannot find a solution for my previous problem ( http://lists.ovirt.org/pipermail/users/2014-July/026255.html) I have decided to export all vms and start over. But when I clic to "export" I get the following message on every single vm (vms are off): *Cannot export VM. Disk configuration (COW Preallocated) is incompatible with the storage domain type.* The storage type is "Shared" Do I need to convert somehow the vms ? Thank you Fabien Carré

2 3

oVirt 3.5 2 nd test day report
by Maor Lipchuk 31 Jul '14

31 Jul '14

Hi all, I've been testing again two features: 1) The first feature was: [RFE] Maintenance operations on a VM would ask for an optional reason The feature provides the ability to present a message to the user regarding the reason why this VM has been shutdown. It seems that there is still an issue that the comment gets deleted when shutting down the VM while the VM is powering up or shutting down. I also found a new issue when shutting down a VM while it is suspended, this also does not save the reason. 2) The other feature I was testing was: Allow to clone a (down) VM without snapshot/template This feature provides the ability to clone a VM from the VM itself, instead do it from a snapshot. It seems that now it's just don't work, I'm getting the following error ACTION_TYPE_FAILED_TEMPLATE_NOT_EXISTS_IN_CURRENT_DC every time. I suspect it is a regression from commit c45b3616ef711d5b46e89a1f5b12533a2698425e. I think the origin of this failure is that since the blank Template is on the default DC, and the VM, I created, was on another DC, we get this CDA message. opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1125196 Regards, Maor

1 0

oVirt 3.5 test day 2 results: foreman advanced integration feature
by Moti Asayag 31 Jul '14

31 Jul '14

Hi, In the second ovirt test day I've retested the foreman advanced integration. Using the instructions on the wiki page I was able to test part of the feature: * Adding foreman provider and test connectivity with certificates import * Present discovered hosts by foreman * Present provisioned hosts by foreman * Add discovered hosts by foreman (reached to "Installing OS" phase only due to environmental issues). Since the host provisioning wasn't completed, I haven't reach to test the foreman-->ovirt connectivity which should have trigger the host installation. I've filed a couple of bugs which I encountered during the testing: Bug 1124870 - Provision of a host without compute resources fails with NPE Bug 1124878 - "Set Root password" text label is not aligned with its caption Bug 1124891 - [oVirt][Foreman] Root password length should be validated Bug 1124887 - [RFE][oVirt][Foreman] Improve error messages when action fails on foreman server In addition I've updated the feature page which missed a required package to be installed on the foreman server. Regards, Moti ----- Forwarded Message ----- From: "Moti Asayag" <masayag(a)redhat.com> To: devel(a)ovirt.org Sent: Thursday, July 3, 2014 5:17:11 PM Subject: ovirt test day report - ovirt - foreman advanced integration feature Hi, I assigned myself to the ovirt-foreman advanced integration feature [1] in the first ovirt 3.5 test day. The setup required for testing that environment is a bit complex (foreman, isolated network, extending the foreman with extra plugins). I faced environmental issues most of the day, mainly regarding foreman installation and configuration. I provided specific feedback regarding the installed setup missing steps to Yaniv, the feature owner, which will incorporate them into the feature page. I haven't reached into a point where i can provision a host via foreman into ovirt, but I plan to get back to it in the second ovirt test day (or even before). [1] http://www.ovirt.org/Features/AdvancedForemanIntegration Regards, Moti

2 1

Can't attach storage domain / Unsupported watchdog
by Andrew Lau 31 Jul '14

31 Jul '14

Hi, I'm trying out some new boards (Intel Avotons), and it appears wdmd does not like the watchdog device it provides. Everything in oVirt 3.4.3 seems to run fine until it comes to adding a storage device. It gives me an error about Cannot acquire host id vdsm logs, http://fpaste.org/122164/67695431/ # service wdmd start (logs) wdmd[14062]: wdmd started S0 H1 G0 wdmd[14062]: /dev/watchdog failed to set timeout wdmd[14062]: /dev/watchdog disarmed wdmd[14062]: no watchdog device, load a watchdog driver # service wdmd status wdmd dead but subsys locked I can't seem to find any documentation on what wdmd does, could someone explain? Thanks, Andrew

2 2

oVirt 3.5 test day 2 results
by Francesco Romani 31 Jul '14

31 Jul '14

Hi everyone, Hi tested again http://www.ovirt.org/Features/WebSocketProxy_on_a_separate_host What happened on tast day 1 * found minor packaging issues * stopped earlier facing SSL issues, had a followup the day after an managed to have the feature working. This time things got better, and again the feature works as expected. The packaging issues are gone, but I still had UX annoyances along the way. I followed instructions on the wiki page above. Platform: F20 hypervisor host F20 engine host F19 websocket proxy (Didn't had time to test on different platforms because local bandwith issues eat lot of time just to install things) Installation went fine. websocket proxy setup is maybe a bit clumsy (I mean the text mode wizard), but it is bearable (I don't mind at all, but someone else can...); for some reasons (I cannot exclude an error from mine) engine got configured to use localhost as websocket proxy. To fix this I edited the engine config (update on DBMS), but then faced this error on proxy side: Jul 29 17:13:14 shinji ovirt-websocket-proxy.py[17004]: 1: handler exception: [Errno 1] _ssl.c:504: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher to redo the websocket setup I removed (actually renamed) /etc/pki/ovirt-engine and rerun setup. After that everything worked fine Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 8: connecting to: 192.168.1.53:5900 (using SSL) Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 5: 192.168.1.177: SSL/TLS (wss://) WebSocket connection Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 5: 192.168.1.177: Version hybi-13, base64: 'False' Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 5: 192.168.1.177: Path: '/eyJ2YWxpZFRvIjoiMjAxNDA3MjkxNTIx [...] 192.168.1.53 is the hypervisor host I used Now the point is maybe I did some mistakes or overlooked some configuration steps (maybe blindly hit return instead of changing a default), but I suggest to improve the docs/wiki to document how to fix common gotchas and/or to reconfigure things. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

3 6

Re: [ovirt-users] el7 hosts? el7 node iso?
by Alexander Ludas 31 Jul '14

31 Jul '14

I can confirm that. EL7 with vdsm from 3.4.3 seems to run fine, at least for basic tasks. (Start/Stop/Spice/Import/Export) I also run EL7 as node for hosted engine, but I had to rebuild all the necessary packages myself. otopi-1.2.2-1 ovirt-host-deploy-1.2.2-0.0.master.20140624063031.gitf0ac297 ovirt-hosted-engine-ha-1.1.6-0.1.master.20140722094509.gitd8c3b3c ovirt-hosted-engine-setup-1.1.6-0.0.master.20140716142616.gita533ea3 Regards, Alex -----Original message----- > From:Jorick Astrego <j.astrego(a)netbulae.eu> > Sent: Wednesday 30th July 2014 21:45 > To: users(a)ovirt.org > Subject: Re: [ovirt-users] el7 hosts? el7 node iso? > > > > On 07/30/2014 02:10 PM, Paul Jansen > wrote: > > I see from here - > https://fedorahosted.org/ovirt/ticket/123 <https://fedorahosted.org/ovirt/ticket/123> - that vdsm is now > building OK on el7. > > What are the plans for el7 and oVirt 3.5? I seem to recall > hearing that there was a hope that there would be some initial > support by the time oVirt 3,5 release comes around. > > I understand that there are functional tests for vdsm, but that > these tests are not complete. > > Are these tests running on an el7 jenkins slave at this point? > > Is there likely to be an el7 node iso spin in the near future? > > I'm super keen to know whether live snapshots/storage migration > works with oVirt 3.5 and el7 hosts. Has anyone got any info? > > We have Centos 7 ovirt nodes deployed and connected to ovirt engine. > Everything looks fine for now, but I will start testing tomorrow and > post the results when we know more. > > Kind regards, > > Jorick Astrego > > Netbulae B.V. > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > >

2 1

REQUEST: MD5 for images
by Jaco 31 Jul '14

31 Jul '14

I downloaded the latest Live ISO image I could find - ovirt-live-el6-3.4.3-1.iso - but it's not working as expected. I'd like to request form the repo maintainers to add MD5sum's to the service so that I can verify the integrity of the images I'm running. Cheers - Jaco

4 4

oVirt Weekly Sync Meeting Minutes: July 30, 2014
by Brian Proffitt 30 Jul '14

30 Jul '14

========================= #ovirt: oVirt Weekly Sync ========================= Meeting started by bkp at 14:01:49 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-07-30-14.01.log.html . Meeting summary --------------- * Agenda and Roll Call (bkp, 14:02:05) * infra update (bkp, 14:02:55) * 3.4.z updates (bkp, 14:02:55) * 3.5 status (bkp, 14:02:55) * conferences and workshops (bkp, 14:02:55) * other topics (bkp, 14:02:55) * infra update (bkp, 14:03:46) * infra Networking almost ready on phx machines, I'm right now installing all the hosts (starge servers and 1 host are already up) (bkp, 14:07:33) * infra Hopefully ready this week for spawning VMs (bkp, 14:07:33) * infra misc should be available in a few weeks to help a bit more with infra tickets. (bkp, 14:08:42) * 3.4.z updates (bkp, 14:09:17) * 3.4.z updates We're going to start composing oVirt 3.4.4 RC on *2014-09-09 08:00 UTC* from 3.4 branch. (bkp, 14:09:39) * 3.4.z updates Bug tracker at http://bugzilla.redhat.com/1118689 shows no open blockers for 3.4.4. (bkp, 14:09:39) * 3.4.z updates There are still 14 bugs targeted to 3.4.4. Excluding node and documentation bugs we still have 7 bugs targeted to 3.4.4. (bkp, 14:09:39) * 3.4.z updates For a complete report, see http://lists.ovirt.org/pipermail/users/2014-July/026385.html (bkp, 14:09:39) * 3.5 status (bkp, 14:11:08) * 3.5 status integration oVirt 3.5.0 RC will be composed on Mon * 2014-08-04 08:00 UTC*. (bkp, 14:11:42) * 3.5 status integration There are still six blockers for 3.5 http://bugzilla.redhat.com/1073943 (3 infra, 1 network, 1 node, 1 storage) [To be reviewed in individual teams' reports later in this meeting.] (bkp, 14:11:42) * 3.5 status integration These six blockers should be fixed before RC: there's no point in trying to compose a release candidate that doesn't match release criteria (bkp, 14:11:42) * 3.5 status integration There are still 397 bugs targeted to 3.5.0. Excluding node and documentation bugs we still have 349 bugs targeted to 3.5.0. (bkp, 14:11:42) * 3.5 status integration The time has come to decide if postpone the bugs to next release or postpone the release again. (bkp, 14:11:46) * 3.5 status integration For a complete report, see http://lists.ovirt.org/pipermail/users/2014-July/026386.html (bkp, 14:11:49) * 3.5 status virt Small bug with virtio-rng and EL 6.5-based hosts, fix ETA this week. (bkp, 14:19:29) * 3.5 status storage Finishing live-merge detection of host caps (patch already posted, has some problems that need to be addressed) (bkp, 14:24:40) * 3.5 status storage Drilling away at bugs. (bkp, 14:24:41) * 3.5 status storage BZ 1124498 May be an infra issue, investigating. (bkp, 14:24:41) * 3.5 status infra BZ 1115152 - was reopened. It should be done tomorrow the latest (bkp, 14:35:24) * 3.5 status infra BZ 1115044 - needs to be merged. It was already acknowledged (bkp, 14:35:24) * 3.5 status infra BZ 1124141 - Martin already posted the change there are 2 acks but no verify flag. He is offline I will ask him tomorrow about it (bkp, 14:35:24) * 3.5 status network BZ 1114987 - Moved to ON QA earlier today (bkp, 14:38:28) * 3.5 status network All is else good, nothing painful surfacing from 2nd Test Day (yet) (bkp, 14:38:28) * 3.5 status sla Still working and concentrated in merging blkio feature u/s, most of the remaining work is UI code review, and probably some missing patches in MOM. (bkp, 14:42:02) * 3.5 status sla NUMA: Positive feedback in testday, next week we should continue testing it; UI work is in progress, and should reveal/verify some more issues. (bkp, 14:42:02) * 3.5 status node The generic registration needs more work. It's likely to be delayed to 3.6. (bkp, 14:43:11) * 3.5 status node The appliance needs an CI update/fixed (bkp, 14:43:11) * 3.5 status node Hosted engine plugin blocker: needs more testing. No ETA mentioned. (bkp, 14:43:11) * 3.5 status vdsm Nothing to report on 3.5. (bkp, 14:47:45) * 3.5 status vdsm dhclient bug needs to be backported to 3.5 (bkp, 14:50:47) * 3.5 status gluster Looking at bugs piotr logged during second test day (bkp, 14:52:28) * 3.5 status ux GUI sorting: same as last week - sub-tabs sorting within 'virt' main tabs is still in progress. full status is in: https://docs.google.com/spreadsheets/d/1S3qDYqv9OK5ruI41RpFpRAsLaojpGL-W6WY… (bkp, 14:56:06) * 3.5 status ux Italian translation is still in ~30% completion. ecohen|mtg has pinged for status. (bkp, 14:56:06) * 3.5 status ux Translations were updated in 'master' and in 'ovirt-engine-3.5' [merged] (bkp, 14:56:06) * 3.5 status ux Additional GUI sorting bugs to be assigned. (bkp, 14:56:53) * Conferences and Workshops (bkp, 14:57:12) * Conferences and Workshops I have been tasked to organize Infrastructure.Next in Chicago during LinuxCon (Aug 20-22), so we have an opportunity to get a bit more oVirt content in there. (bkp, 14:57:32) * Conferences and Workshops Planning for the "Red Hat" day (*not* the official name) at Fossetcon is continuing. (bkp, 14:57:32) * Conferences and Workshops The oVirt Workshop at LinuxCon EU is a go (not new news), so now I need topic ideas for sessions. Please send to bazulay or myself as soon as possible. (bkp, 14:57:32) * Other Topics (bkp, 14:58:17) Meeting ended at 15:01:39 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bkp (111) * mskrivanek (12) * awels (9) * lvernia (8) * amureini_ (7) * gchaplik (7) * danken (6) * pkliczew (5) * apuimedo (4) * dcaro (3) * tiraboschi (3) * sahina (2) * ovirtbot (2) * eedri (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

5 7

el7 hosts? el7 node iso?
by Paul Jansen 30 Jul '14

30 Jul '14

---1504104896-368636363-1406722222=:60154 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I see from here - https://fedorahosted.org/ovirt/ticket/123 - that vdsm is = now building OK on el7.=0AWhat are the plans for el7 and oVirt 3.5? I seem = to recall hearing that there was a hope that there would be some initial su= pport by the time oVirt 3,5 release comes around.=0A=0AI understand that th= ere are functional tests for vdsm, but that these tests are not complete.= =0AAre these tests running on an el7 jenkins slave at this point?=0A=0AIs t= here likely to be an el7 node iso spin in the near future?=0A=0AI'm super k= een to know whether live snapshots/storage migration works with oVirt 3.5 a= nd el7 hosts.=A0 Has anyone got any info? ---1504104896-368636363-1406722222=:60154 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:He= lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;fo= nt-size:12pt">I see from here - https://fedorahosted.org/ovirt/ticket/123 -= that vdsm is now building OK on el7. What are the plans for el7 and oVi= rt 3.5? I seem to recall hearing that there was a hope that there would be = some initial support by the time oVirt 3,5 release comes around. I u= nderstand that there are functional tests for vdsm, but that these tests ar= e not complete. Are these tests running on an el7 jenkins slave at this = point? Is there likely to be an el7 node iso spin in the near future= ? I'm super keen to know whether live snapshots/storage migration wo= rks with oVirt 3.5 and el7 hosts.  Has anyone got any info? </d= iv></body></html> ---1504104896-368636363-1406722222=:60154--

2 1

oVirt 3.5 test day: retrying failed fencing
by Martin Mucha 30 Jul '14

30 Jul '14

Hi, I've tested: "Bug 1090511 [RFE] Improve fencing robustness by retrying failed attempts". Spoiler alert: Tested feature worked, but fencing was not successful due to bug https://bugzilla.redhat.com/1124141 --- How to setup environment for testing: - 3 hosts are required, at least two of them with PM enabled. - 2 hosts (A, B), with pm enabled, should be with one cluster, remaining one (C) in another cluster. Reason for that is that search for fencing proxy is first done in same cluster, only if there's none host available, hosts outside of this cluster is considered; this separation is needed to make sure that right (not working) fencing proxy is selected first. notation: host A ~ defective host to be fenced host B ~ first selected fencing proxy, which will fail fencing host A. host C ~ second selected fencing proxy, which should succeed fencing host A. A and B are in same cluster. process: 1. On host B we alter iptables, so it cannot contact host A and fence it. SSH was blocked to disallow soft fencing and ipmi was blocked to disallow 'hard' fencing. iptables -A OUTPUT -p udp -d 10.34.63.198 --dport 623 -j DROP iptables -A OUTPUT -p tcp -d 10.34.63.178 --dport 22 -j DROP 2. On host A was removed rules allowing connection to vdsm [1] and vdsm was restarted vdsm[2] so all ssh connections needs to be reopened. That makes engine think, that host is down/overloaded. drop rule: ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:54321 followed by systemctl restart vdsmd Result: After restart of vdsmd engine recognised host A as iresponsive, and tried to fence it. First attempt to fence host A was performed by host B and failed as expected, second attempt to fence host A performed by host C and from code perspective succeeded. Error message [1] correctly displayed. However fence was not successful due to bug https://bugzilla.redhat.com/1124141 which causes java.lang.StackOverflowError. Code related to this bug should be OK, but will be working only after mentioned bug is fixed. M. [1]. Fencing operation failed with proxy host <ID>, trying another proxy...

1 0