- Users - oVirt List Archives

ovirt node iso?
by Jorick Astrego 01 Aug '14

01 Aug '14

Hi, I wish to test the advanced foreman integration with node deploy again but the node iso available is about a month old. http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/ovirt-node-iso-3.5.0.ovirt… Also it didn't work properly on the first test day.... Doesn't it need testing or is it so broken that an update can't be released at the moment? Kind regards, Jorick Astrego Netbulae

3 3

Need Info and Case study on Ovirt
by Chandrahasa S 01 Aug '14

01 Aug '14

This is a multipart message in MIME format. --=_alternative 00330E7D65257D27_= Content-Type: text/plain; charset="US-ASCII" Dear All, We have setup Ovirt for our Internal usage. Want to give presentation on Ovirt. Please share Presentation on Latest ovirt & case studies if anyone having. Regards, Chandrahasa S Tata Consultancy Services Data Center- ( Non STPI) 2nd Pokharan Road, Subash Nagar , Mumbai - 400601,Maharashtra India Ph:- +91 22 677-81825 Buzz:- 4221825 Mailto: chandrahasa.s(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --=_alternative 00330E7D65257D27_= Content-Type: text/html; charset="US-ASCII" Dear All, We have setup Ovirt for our Internal usage. Want to give presentation on Ovirt.  Please share Presentation on Latest ovirt & case studies if anyone having. Regards, Chandrahasa S Tata Consultancy Services Data Center- ( Non STPI) 2nd Pokharan Road, Subash Nagar , Mumbai - 400601,Maharashtra India Ph:- +91 22 677-81825 Buzz:- 4221825 Mailto: chandrahasa.s(a)tcs.com Website: <a href=http://www.tcs.com/>http://www.tcs.com</a> ____________________________________________ Experience certainty.        IT Services                        Business Solutions                        Consulting ____________________________________________=====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --=_alternative 00330E7D65257D27_=--

2 1

update to 3.4.3
by Kapetanakis Giannis 01 Aug '14

01 Aug '14

Hi, I'm trying to upgrade from 3.4.2 to 3.4.3 on Centos 6 x86_64 and one of the packages is not signed. # yum update ovirt-engine-setup ovirt-engine-reports-setup ovirt-engine-dwh-setup Dependencies Resolved ============================================================================================================================ Package Arch Version Repository Size ============================================================================================================================ Updating: ovirt-engine-dwh-setup noarch 3.4.3-1.el6 ovirt-3.4-stable 51 k ovirt-engine-reports-setup noarch 3.4.3-1.el6 ovirt-3.4-stable 54 k ovirt-engine-setup noarch 3.4.3-1.el6 ovirt-3.4-stable 4.2 k Updating for dependencies: otopi noarch 1.2.2-1.el6 ovirt-3.4-stable 133 k otopi-java noarch 1.2.2-1.el6 ovirt-3.4-stable 23 k ovirt-engine-lib noarch 3.4.3-1.el6 ovirt-3.4-stable 20 k ovirt-engine-setup-base noarch 3.4.3-1.el6 ovirt-3.4-stable 94 k ovirt-engine-setup-plugin-ovirt-engine noarch 3.4.3-1.el6 ovirt-3.4-stable 134 k ovirt-engine-setup-plugin-ovirt-engine-common noarch 3.4.3-1.el6 ovirt-3.4-stable 22 k ovirt-engine-setup-plugin-websocket-proxy noarch 3.4.3-1.el6 ovirt-3.4-stable 13 k Transaction Summary ============================================================================================================================ Upgrade 10 Package(s) Package ovirt-engine-reports-setup-3.4.3-1.el6.noarch.rpm is not signed regards, Giannis

4 6

Testday: json rpc
by Antoni Segura Puimedon 31 Jul '14

31 Jul '14

Hi fellow oVirters, On this test day I picked JSON RPC for testing: My initial environment consisted of a hosted engine setup with three hosts. Upgrading =========== The first task, then, was to upgrade everything to 3.5. My guide was http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine One issue that I encountered was that after setting the 3.5 pre-release yum repo on the engine VM and doing yum update, when doing engine-setup To make it handle the upgrade, that failed complaining about missing a package called patternfly1. I remembered that on the list Greg Sheremeta mentioned a copr repository for it, so I went ahead, installed it and repeated the engine-setup This time it succeeded, however I feel like patternfly1 should probably be an ovirt-engine-3.5 dependency and it should be in the ovirt 3.5 repository. I also noticed that after upgrading the hosts the amount of free system memory is much lower, while the VMs continue to run fine. I opened: https://bugzilla.redhat.com/1124451 Another thing that happened was that restarting ovirt-ha-agent and ovirt-ha-broker using systemd fails silently and it says that they were killed. I only got it to work again by doing: /lib/systemd/systemd-ovirt-ha-broker restart /lib/systemd/systemd-ovirt-ha-agent restart However, and obviously, doing it like that escapes from the advisable control of systemd. Another bad thing is that after doing all this we get that the current host (which has the engine running displays): --== Host 2 status ==-- Status up-to-date : False Hostname : 10.34.63.180 Host ID : 2 Engine status : unknown stale-data Score : 2000 Local maintenance : False Host timestamp : 1406640293 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1406640293 (Tue Jul 29 15:24:53 2014) host-id=2 score=2000 maintenance=False bridge=True cpu-load=0.0856 engine-health={"health": "good", "vm": "up", "detail": "up"} gateway=True mem-free=3192 Why did the engine status go to unknown stale-data? (it also happened for the other two hosts in the setup. Changing hosts to use JSON RPC =============================== After talking with Piotr and trying it with the webadmin UI, I found out that there is no direct way to update a host's settings to use json rpc as its connectivity mechanism with the engine. This constitutes a usabiltiy bug which I filed: https://bugzilla.redhat.com/1124442 It is presumable that users will want to move to the newer and better RPC mechanism and they should be able to do so by merely putting the host in maintenance and ticking some checkbox in the 'edit host' dialog. I did the workaround of removing the host and adding it again and that worked, the host went up. Network operations via JSON RPC ================================ After the host went up, I decided to send a setupNetworks command. The operation worked out fine, but unfortunately we have a very serious gap that makes it impossible for me to use jsonrpc for network operations/development. **Logging** When doing a network operation with xmlrpc we'd get the following in vdsm.log Thread-21::DEBUG::2014-07-30 13:38:11,414::BindingXMLRPC::1127::vds::(wrapper) client [10.34.61.242]::call setupNetworks with ({'10': {'nic': 'em2', 'vlan': '10', 'STP': 'no', 'bridged': 'true', 'mtu': '1500'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}) {} flowID [686033d4] Thread-21::DEBUG::2014-07-30 13:38:32,689::BindingXMLRPC::1134::vds::(wrapper) return setupNetworks with {'status': {'message': 'Done', 'code': 0}} As you can see, we get the bare minimum logging one could ask for, an entry with the command called and the data it received and another entry with the return result data. Doing the same with jsonrpc (and ignoring the excessive IOProcess) if I search for "setupNetworks" the only thing I get is: Thread-23057::DEBUG::2014-07-30 13:32:44,126::__init__::462::jsonrpc.JsonRpcServer::(_serveRequest) Looking for method 'Host_setupNetworks' in bridge And if I search for the data received, like 'STP', there is nothing whatsoever. As I said, unless this is fixed and we get entries with the same amount of data as before, it can't be used in production nor in development. https://bugzilla.redhat.com/1124813 TL;DR: - lack of usability upgrading an environment to use jsonrpc https://bugzilla.redhat.com/1124442 - Failure on step 7 of upgrade steps: https://bugzilla.redhat.com/1124826 - JSON RPC logging excessive but insuficient for network call debugging https://bugzilla.redhat.com/1124813

3 4

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