<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="GENERATOR" content="GtkHTML/4.6.4">
</head>
<body>
ons 2013-10-30 klockan 13:45 +0000 skrev Dan Kenigsberg:
<blockquote type="CITE">
<pre>
On Wed, Oct 30, 2013 at 03:24:56PM +0200, Itamar Heim wrote:
<font color="#737373">> On 10/30/2013 03:10 PM, Karli Sjöberg wrote:</font>
<font color="#737373">> >ons 2013-10-30 klockan 15:05 +0200 skrev Itamar Heim:</font>
<font color="#737373">> >>On 10/30/2013 11:12 AM, Karli Sjöberg wrote:</font>
<font color="#737373">> >>> ons 2013-10-30 klockan 09:16 +0100 skrev Vinzenz Feenstra:</font>
<font color="#737373">> >>>> On 10/30/2013 07:09 AM, Karli Sjöberg wrote:</font>
<font color="#737373">> >>>></font>
<font color="#737373">> >>>>> tis 2013-10-29 klockan 15:48 +0100 skrev Vinzenz Feenstra:</font>
<font color="#737373">> >>>>>> On 10/29/2013 03:06 PM, Karli Sjöberg wrote:</font>
<font color="#737373">> >>>>>></font>
<font color="#737373">> >>>>>>> tis 2013-10-29 klockan 14:48 +0100 skrev Vinzenz Feenstra:</font>
<font color="#737373">> >>>>>>>> On 10/29/2013 02:37 PM, Karli Sjöberg wrote:</font>
<font color="#737373">> >>>>>>>></font>
<font color="#737373">> >>>>>>>>> tis 2013-10-29 klockan 14:30 +0100 skrev René Koch (ovido):</font>
<font color="#737373">> >>>>>>>>>> On Tue, 2013-10-29 at 13:23 +0000, Karli Sjöberg wrote:</font>
<font color="#737373">> >>>>>>>>>> > tis 2013-10-29 klockan 14:15 +0100 skrev René Koch (ovido):</font>
<font color="#737373">> >>>>>>>>>> > > Hi,</font>
<font color="#737373">> >>>>>>>>>> > ></font>
<font color="#737373">> >>>>>>>>>> > > I have some issues with ovirt-guest-agent as no information is reported</font>
<font color="#737373">> >>>>>>>>>> > > from guest-agent to oVirt webadmin anymore.</font>
<font color="#737373">> >>>>>>>>>> > > I'm unsure when I lost the information - I know for sure it worked last</font>
<font color="#737373">> >>>>>>>>>> > > month when I tested the guest agent packages for Debian and Ubuntu.</font>
<font color="#737373">> >>>>>>>>>> > ></font>
<font color="#737373">> >>>>>>>>>> > > Status now is that I don't receive any data.</font>
<font color="#737373">> >>>>>>>>>> > > I have the following test vms:</font>
<font color="#737373">> >>>>>>>>>> > > * RHEL 6 with rhevm-guest-agent 1.0.7 (RHEV repository)</font>
<font color="#737373">> >>>>>>>>>> > > * RHEL 6 with ovirt-guest-agent 1.0.8 (EPEL)</font>
<font color="#737373">> >>>>>>>>>> > > * openSUSE 12.3 with ovirt-guest-agent 1.0.8.1 (self compiled)</font>
<font color="#737373">> >>>>>>>>>> > ></font>
<font color="#737373">> >>>>>>>>>> > > Both RHEL server reported information (memory, ip-address,...)</font>
<font color="#737373">> >>>>>>>>>> > > previously.</font>
<font color="#737373">> >>>>>>>>>> > > The only changes which could broke the guest agent communication are</font>
<font color="#737373">> >>>>>>>>>> > > updates on the CentOS host and the engine.</font>
<font color="#737373">> >>>>>>>>>> > ></font>
<font color="#737373">> >>>>>>>>>> > > Can you give me some hints how to troubleshoot the guest agent? I can't</font>
<font color="#737373">> >>>>>>>>>> > > find any information (or don't know the right pattern to search for) in</font>
<font color="#737373">> >>>>>>>>>> > > vdsm.log and engine.log. Guest agent is running in the vms, but doesn't</font>
<font color="#737373">> >>>>>>>>>> > > log anything except start and stop of the service (can I change the</font>
<font color="#737373">> >>>>>>>>>> > > handler_logfile args for more debugging and if yes how?):</font>
<font color="#737373">> >>>>>>>>>> > ></font>
<font color="#737373">> >>>>>>>>>> > > # tail /var/log/ovirt-guest-agent/ovirt-guest-agent.log</font>
<font color="#737373">> >>>>>>>>>> > > MainThread::INFO::2013-10-29</font>
<font color="#737373">> >>>>>>>>>> > > 11:00:15,340::ovirt-guest-agent::37::root::Starting oVirt guest agent</font>
<font color="#737373">> >>>>>>>>>> > ></font>
<font color="#737373">> >>>>>>>>>> > > Btw, I'm running oVirt 3.2.3...</font>
<font color="#737373">> >>>>>>>>>> ></font>
<font color="#737373">> >>>>>>>>>> > This has happened for me in the past and putting the Host in</font>
<font color="#737373">> >>>>>>>>>> > maintenance and then restarting the vdsmd solved it.</font>
<font color="#737373">> >>>>>>>>>> ></font>
<font color="#737373">> >>>>>>>>>> > /Karli</font>
<font color="#737373">> >>>>>>>>>></font>
<font color="#737373">> >>>>>>>>>></font>
<font color="#737373">> >>>>>>>>>> Thanks a lot Karli - restarting vdsmd did the trick!</font>
<font color="#737373">> >>>>>>>>></font>
<font color="#737373">> >>>>>>>>> Well, even a broken clock can be right. Even twice a day:)</font>
<font color="#737373">> >>>>>>>>></font>
<font color="#737373">> >>>>>>>>> @developers</font>
<font color="#737373">> >>>>>>>>> Is this something you have noticed as well? I mean, that</font>
<font color="#737373">> >>>>>>>>> sometimes vdsmd needs this manual kick? Where do you start</font>
<font color="#737373">> >>>>>>>>> debugging when this issue occurs, restarting the daemon once in a</font>
<font color="#737373">> >>>>>>>>> while is just the quickfix, I´d like to solve it once and for all.</font>
<font color="#737373">> >>>>>>>> Yeah there have been applied multiple fixes in that regard already.</font>
<font color="#737373">> >>>>>>>></font>
<font color="#737373">> >>>>>>>><a href="https://github.com/oVirt/vdsm/commit/5b5c58580e20ffaf3ceff7193f4c28cbadd8c42f">https://github.com/oVirt/vdsm/commit/5b5c58580e20ffaf3ceff7193f4c28cbadd8c42f</a></font>
<font color="#737373">> >>>>>>>> and</font>
<font color="#737373">> >>>>>>>><a href="https://github.com/oVirt/vdsm/commit/26bfc74765aed35af6d17cfad1ed8115eef650f1">https://github.com/oVirt/vdsm/commit/26bfc74765aed35af6d17cfad1ed8115eef650f1</a></font>
<font color="#737373">> >>>>>>>></font>
<font color="#737373">> >>>>>>>> So it looks like that both of you are using oVirt 3.1, which</font>
<font color="#737373">> >>>>>>>> contains neither of those two fixes. AFAIK only the first one is</font>
<font color="#737373">> >>>>>>>> in oVirt 3.2 and the second one is in oVirt 3.3</font>
<font color="#737373">> >>>>>>></font>
<font color="#737373">> >>>>>>> Öhm:</font>
<font color="#737373">> >>>>>>> ovirt-engine-3.2.2-1.1.43.el6.noarch</font>
<font color="#737373">> >>>>>>></font>
<font color="#737373">> >>>>>>> And René already stated running 3.2.3</font>
<font color="#737373">> >>>>>> Hmm interesting, but that VDSM version is not 3.2? Did you upgrade</font>
<font color="#737373">> >>>>>> your hypervisors?</font>
<font color="#737373">> >>>>></font>
<font color="#737373">> >>>>> All systems are as upgraded as they can be, and dc/cluster is running</font>
<font color="#737373">> >>>>> in 3.2-mode. Probably since I´m running dreyou´s repo (and perhaps</font>
<font color="#737373">> >>>>> René as well), the versions may be different from what´s in yours?</font>
<font color="#737373">> >>>> Sorry my bad, I messed up the correlation with the versions. I thought</font>
<font color="#737373">> >>>> 4.10.3 is 3.1 but it is really 3.2.</font>
<font color="#737373">> >>>> So this issues are fixed with 3.3 where I would wait with the upgrade</font>
<font color="#737373">> >>>> until it was finally stabilized.</font>
<font color="#737373">> >>></font>
<font color="#737373">> >>> Yepp yepp, that´s what I was thinking as well. About when would you</font>
<font color="#737373">> >>> think 3.3 has stabilized, 3.3.1?</font>
<font color="#737373">> >></font>
<font color="#737373">> >>a few days hopefully.</font>
<font color="#737373">> ></font>
<font color="#737373">> >"a few days"*™* ;)</font>
<font color="#737373">> ></font>
<font color="#737373">> >>note since the bug is on vdsm, upgrading vdsm should resolve it,</font>
<font color="#737373">> >>regardless of upgrading engine, dc/cluster levels, etc.</font>
<font color="#737373">> ></font>
<font color="#737373">> >That´s good to know, thanks! And you are completely confident that there</font>
<font color="#737373">> >is proper backwards compatibility? Has anyone tested?</font>
<font color="#737373">> </font>
<font color="#737373">> vdsm is supposed to always keep backward compatibility. i think one</font>
<font color="#737373">> issue was found in 3.3 around live migration in a 3.2 cluster (i.e.,</font>
<font color="#737373">> mixed versions of 3.2 vdsm and 3.3 vdsm)</font>
<font color="#737373">> danken - was this fixed in 3.3.1 vdsm?</font>
There has been a breakage of migration between master and ovirt-3.3.0.
Fixing it was my gating issue for the ovirt-3.3 rebase, and that's done
for a couple of weeks.
I've tested 3.3.0<->3.3.1 migration then, and I am not aware of any
more recent problem. (However, when it comes to migration, I'm sure a
bug or two are lurking somewhere....)
</pre>
</blockquote>
<br>
Excellent! But just to be sure, I´ll make sure to upgrade vdsm in our test environment before applying it in production, just for Murphy´s sake;)<br>
<br>
<table cellspacing="0" cellpadding="0" width="100%">
<tbody>
<tr>
<td>-- <br>
<br>
Med Vänliga Hälsningar<br>
-------------------------------------------------------------------------------<br>
Karli Sjöberg<br>
Swedish University of Agricultural Sciences<br>
Box 7079 (Visiting Address Kronåsvägen 8)<br>
S-750 07 Uppsala, Sweden<br>
Phone: +46-(0)18-67 15 66<br>
<a href="mailto:karli.sjoberg@adm.slu.se">karli.sjoberg@slu.se</a> </td>
</tr>
</tbody>
</table>
</body>
</html>