<= p =3D class=3D3DMsoNormal>Thanks, Joop, for the node platform best practices… I did turn =3D selinux from “enforcing” to “permissive”, and =3D then when I tried to ping the engine by fqdn, I saw that DNS lookups =3D were failing (even tho resolv.conf looked correct…) Did a =3D ‘yum remove NetworkManager” and then fixed the =3D /etc/sysconfig/network-scripts/ifcfg-<nic>, and then after a =3D reboot, I can now see the info for the node in the WUI on the manager, =3D although the status for the node is still “Non =3D Operational”…

Where can I find the node install log (on the engine or the node, and = =3D name?) (Sorry for noob status, but I am a quick learner =3D ;)

Thanks,

Will

From: users-bounces(a)ovirt.org [mailto:users-bounces(a)ovirt.org] On = =3D Behalf Of noc
Sent: Friday, January 17, 2014 3:35 =3D AM
To: users(a)ovirt.org
Subject: Re: [Users] New user = =3D to oVirt, and I haz a sad so far...

On =3D 17-1-2014 8:53, Gabi C wrote:

've been there! =3D :-D
I mean exactly same issuse = =3D you had on Centos, I had on Fedora 19.
Did you disable selinu= x =3D on nodes? 'cause that's what is causing SSh connection =3D closing
My setup:
1 engine on vmware - fedora 19, =3D up-to-date

2 nodes on IBM x series 3650 - =3D fedora 19 based -oVirt Node - 3.0.3 - 1.1.fc19 with nodes beig in =3D glusterfs cluster also.....

Right now, I'm banging my head against "Operation = =3D Add-Disk failed to complete." , message I have got after adding a =3D new virtual machine and try to addd its =3D disk

On Fri, Jan 17, 2014 at 6:08 AM, Will Dennis =3D (Live.com) <willarddennis(a)live.com> wrote:
<= p =3D class=3D3DMsoNormal>Hi all, ready for a story? (well, more of a rant, but = =3D hopefully it will be a
good UX tale, and may even be =3D entertaining.)

Had one of the groups come to me at work this week = =3D and request a OpenStack
setup. When I sat down and discussed their =3D needs, it turns out that they
really only need a multi-hypervisor =3D setup where they can spin up VMs for
their research projects. The VMs = =3D should be fairly long-lived, and will have
persistent storage. Their =3D other request is that the storage should be local
on the hypervisor =3D nodes (they plan to use Intel servers with 8-10 2TB drives
for VM =3D storage on each node.) They desire this in order to keep the VM =3D I/O
local - they do not have a SAN of any sort anyhow, and they do =3D not care
about live migration, =3D etc

@Will
If the installation ends, either = =3D with or without error, it will give you a log location. Upload the log =3D to a paste.bin and mail the link.

@Gabi,
There should be more =3D info in either the vdsm.log on the SPM server or in the engine.log on =3D the engine server, see above for lettings us know what the error =3D is.

Having installed oVirt, probably dozens of times, I have some = =3D guidelines:
- temporarily disable firewalld/iptables (if all works, =3D enable should still work, scripts with rules are generated and location =3D is given)
- make selinux permissive either via setenforce 0 (until =3D next boot) or via /etc/selinux/config ( survives reboots), dont disable =3D it!
- make sure fqdn work in both directions between engine and =3D host(s) (either using /etc/hosts or DNS)
- make sure NetworkManager =3D is disabled and network =3D enabled

Joop