Il 22/03/2019 09:28, Simone Tiraboschi ha scritto:
>
>
> On Fri, Mar 22, 2019 at 9:18 AM Giulio Casella <giulio@di.unimi.it
> <mailto:giulio@di.unimi.it>> wrote:
>
>     Hi guys,
>     I noticed a strange behaviour after updating (part of) my setup to 4.3.2
>     (previously 4.3.1).
>     In detail I have the engine (stand alone, not hosted engine) version
>     4.3.2, and hosts (ovirt-node-ng) are 4.3.2 and 4.3.1.
>
>     In admin portal, VMs running on 4.3.2 hosts report incomplete
>     informations: some of them report no IP address and uptime, none of them
>     report memory, CPU and network usage.
>     Also a couple of VMs stay in "Powering up" state indefinitely
>     (nevertheless the VM is up and running). In this state I can't even
>     migrate the VM.
>
>     VMs running on 4.3.1 hosts, instead, are fine, reporting correct
>     informations.
>
>     For completeness: VMs are a mix of CentOS 7, Fedora, Windows 10, Windows
>     server, ..., with ovirt-guest-agent installed, but the OS seems to make
>     no difference.
>
>     Any ideas?
>
>
> Can you please check /var/log/vdsm/vdsm.log looking for something like
>
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py", line 505, in getGuestInfo
>     del qga['appsList']
> KeyError: 'appsList'
>
> ?
>
> If so, I think it's https://bugzilla.redhat.com/1676893

I confirm I'm in that situation.
I think I will rollback to 4.3.1 and wait for 4.3.3.

Thank you,
Giulio