<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'>On Thu, Nov 15, 2012 at 9:46 AM, Alan Johnson <span dir="ltr"><<a href="mailto:alan@datdec.com" target="_blank">alan@datdec.com</a>></span> wrote:<br><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Nov 15, 2012 at 5:34 AM, Roy Golan <span dir="ltr"><<a href="mailto:rgolan@redhat.com" target="_blank">rgolan@redhat.com</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>logic/flow aside, still the error is on engine side - validating the VdsNetworkInterface entity which</div></div>
seems to be missing an "interfaces" field or method thus throwing this runtime error.<br>
I wonder if GWT serialized something unexpected here.<br>
Alan - can you try invoking setup networks and see if any other action is terminated the same way?</blockquote><div><br></div></div><div>Yes, no matter what I do on Setup Host Networks, I get the same error when I click OK. Even if I make not changes at all, I get the same when I click OK. I have to Cancel to get out of that screen.</div>
</div>
</blockquote></div><br><div>I have just run though the same process on a different engine controlling a single node. Not changing anything on the Setup Host Networks screen, it closes successfully when I click OK. Trying to add the sandbox network to em1 gives the error "Error while executing action Setup Networks: Internal oVirt Engine Error". This shows up in engine.log:</div><font face="courier new, monospace"><<SNIP>></font><br><div><br></div><div><br></div><div id="DWT3910">[A side note: is it wise to keep DEBUG on VDSM logs? If not, is there an easy way to shut it off? That is an awful lot of traffic and might explain why my nodes ran so slow when I was booting off of USB sticks.]</div></blockquote><br>Since you're running off of a USB stick, which is probably limited in write bandwidth (USB interface + flash performance).<br>It would probably be wise to turn it to a higher level, and only turn to
DEBUG when you encounter a problem and can reproduce it (the downside
is that you of course will not log error that you can't reproduce).<br><br>The upside is that you'll save your stick's life (since flash chips have a limited number of writes per cell) and it will work faster (less blocking on log IO until the log is written).<br><br>You can change the log levels in /etc/vdsm/logger.conf<br><br>I would also suggest to turn down libvirt's log level for the same reasons.<br>It seems to me (not sure about this one) that you can do that by adding this line to vdsm.conf:<br>libvirt_log_filters = 2:libvirt 2:remote<br><br><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div></div>
<div><br></div><div>So, all that seems to be consistent with Igor's comments and I'll have to do some fancy dancing to get this setup once I get past the other bug. It would be nice if the GUI relayed the error "<span style="font-family:'courier new',monospace">Setup attached more than one network to nic em1, some of which aren't vlans</span><font id="DWT3950" face="arial, helvetica, sans-serif">" from VDSM to the user, or some clearer translation, but it sounds like that is on the way based on Moti's comments about the nightly's, so I'll let it drop.</font></div></blockquote>This bug was fixed, please see https://bugzilla.redhat.com/show_bug.cgi?id=851134<br><br>In oVirt 3.2 (your DC has to be 3.2 as well) you can change the management network to be VLANd or non-VM network, and use the "Sync Network" feature (part of the setup networks process) to apply the change on the host. Then you'll be able to add a VLAN'd VM network on the same NIC. <br><br>(Remember that if the management network is VLAN'd on the host then it has to be handled somehow so that the engine can communicate with it otherwise you'll lose connectivity to the host)<br><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div><font face="arial, helvetica, sans-serif"></font></div>
<div><br></div><div>This engine and node were built last week and the process went much more smoothly than this first engine having problems. For the problematic engine, which I setup a couple of months ago, the CentOS6 packages had bunch of broken symlinks to jars that were on the system, but not where the symlinks expected them to be. That appears to have been fixed as of least week when I setup this second engine. To fix it on the first, I manually created symlinks where the broken ones were pointed rather than messing with any symlinks created by the packages. </div>
<div><br></div><div>I wonder now if the packages on the bad engine (which are up to date) would have created different symlinks where I did and mine are blocking them from being created. I can rebuild the engine server if needed, but I would appreciate if some one can confirm that this error is consistent with a wrong version of a jar or some similar potential issue. Of course, I would also appreciate if there is a simpler solution. =)</div>
<br>_______________________________________________<br>Users mailing list<br>Users@ovirt.org<br>http://lists.ovirt.org/mailman/listinfo/users<br></blockquote><br></div></body></html>