Thanks for the response!<br><br><div class="gmail_quote">On Sat, Sep 29, 2012 at 8:21 AM, Dave Neary <span dir="ltr"><<a href="mailto:dneary@redhat.com" target="_blank">dneary@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<div class="im"><br>
<br>
On 09/29/2012 01:37 PM, Hans Lellelid wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I apologize in advance that this email is less about a specific<br>
problem and more a general inquiry as to the most recommended /<br>
likely-to-be-successful way path.<br>
</blockquote>
<br></div>
Having just gone through the process, I hope I can help a little! You might want to check (and add to) the Troubleshooting page where I documented the various hiccups I had, and how I addressed them:<br>
<br>
<a href="http://wiki.ovirt.org/wiki/Troubleshooting" target="_blank">http://wiki.ovirt.org/wiki/<u></u>Troubleshooting</a><br>
<br>
There's also "Node Troubleshooting" and "Troubleshooting NFS Storage Issues" which might help you: <a href="http://wiki.ovirt.org/wiki/Node_Troubleshooting" target="_blank">http://wiki.ovirt.org/wiki/<u></u>Node_Troubleshooting</a> and <a href="http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues" target="_blank">http://wiki.ovirt.org/wiki/<u></u>Troubleshooting_NFS_Storage_<u></u>Issues</a><br>
<br>
Also Jason Brooks's "Up and running with oVirt 3.1" article is useful I think: <a href="http://blog.jebpages.com/archives/up-and-running-with-ovirt-3-1-edition/" target="_blank">http://blog.jebpages.com/<u></u>archives/up-and-running-with-<u></u>ovirt-3-1-edition/</a><div class="im">
<br>
<br></div></blockquote><div><br></div><div>I have read a few of those resources, but not the main "Troubleshooting" page, so I will scour the wiki to see if something might help me out.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2nd attempt: I re-installed the nodes as Fedora 17 boxes and<br>
downgraded the kernels to 3.4.6-2. Then I connected these from the<br>
Engine (specifying the root pw) and watched the logs while things<br>
installed. After reboot neither of the servers were reachable.<br>
Sitting in front of the console, I realized that networking was<br>
refusing to start; several errors printed to the console looked like:<br>
</blockquote>
<br></div>
When you say that they are not reachable, what do you mean? By default, installing F17 as a node sets the iptables settings to:<br>
<snip><br></blockquote><div><br></div><div>I mean, that the network interfaces cannot be brought up, not an iptables issue. Sitting (well, standing, they're rack-mounted) in front of the servers yields the multipath errors I mention when trying to start networking. What I started doing (and will likely continue to pursue) is running etc under source control and start combing through the changes that are introduced when I do the remote setup from the engine to see if I can pick apart where it's going south.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So if you're trying to ping the nodes, you should see nothing, but ssh, snmp and vdsm should be available. If you have a local console access to the nodes, you should check the IPTables config.<br>
<br>
I don't understand why you would lose your network connection entirely, though. I don't think that the network config for the nodes is changed by the installer.<div class="im"><br></div></blockquote><div><br></div>
<div>Yeah, it's definitely changed by the installer. The installer sets up the ovirt-bridge (I think that is what it was called) and changes the primary interfaces to reference the bridge, etc. I didn't seen anything obviously wrong with the setup, but clearly it was not working. (I also didn't know exactly what I was starting from, so that is my mistake and I should be able to approach the next time with more confidence.) I did the bridge setup manually myself for attempt #3 and didn't have any problems.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3rd attempt: I re-installed the nodes with Fedora 17 and attempted to<br>
install VDSM manually by RPM. Despite following the instructions to<br>
turn off ssl (ssl=false in /etc/vdsm/vdsm.conf), I am seeing SSL<br>
"unknown cert" errors from the python socket server with every attempt<br>
of the engine to talk to the node.<br>
</blockquote>
<br></div>
Hopefully the "Node Troubleshooting" page (or somebody else) can help you here, I'm afraid I can't.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The<br>
Fedora-17-installed-by-engine sounds good, but there's a lot of magic<br>
there & it obviously completely broke my systems. Is that where I<br>
should focus my efforts? Should I ditch NFS storage and just try to<br>
get something working with local-only storage on the nodes? (Shared<br>
storage would be a primary motivation for moving to ovirt, though.)<br>
</blockquote>
<br></div>
I would focus on this approach, and would continue to aim to use NFS storage. It works fine as long as you are on the 3?4?x kernels.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am very excited for this to work for me someday. I think it has<br>
been frustrating to have such sparse (or outdated?) documentation and<br>
such fundamental problems/bugs/configuration challenges. I'm using<br>
pretty standard (Dell) commodity servers (SATA drives, simple RAID<br>
setups, etc.).<br>
</blockquote>
<br></div>
The "Quick Setup Guide" was useful to me, as long as everything went well: <a href="http://wiki.ovirt.org/wiki/Quick_Start_Guide" target="_blank">http://wiki.ovirt.org/wiki/<u></u>Quick_Start_Guide</a><br>
<br>
Hope some of that is helpful!<br><br></blockquote><div><br></div><div>I will take a look a that guide -- not sure if I've read that one yet. I will follow back up with what I learn / what works so it might help others. If there's a way that I can update the wiki to help those in my specific predicament, I will do that too. (It's possible there is something about my [Dell] hardware that is not compatible with oVirt's default installer, etc.)</div>
<div><br></div><div>Thanks,</div><div>Hans</div></div>