I see you are using the engine version 4.3.7.2, but this fix is in vdsm,
since version:
vdsm-4.30.34


On Wed, 29 Jan 2020 at 10:03, Andrej Krejcir <akrej...@redhat.com> wrote:

> Hi,
>
> you have probably hit this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1749630
>
> It has been fixed in version 4.3.7.2.
>
>
> Best regards,
> Andrej
>
> On Wed, 29 Jan 2020 at 09:45, Divan Santana <di...@santanas.co.za> wrote:
>
>>
>> > I've seen similar behavior before.  Have you tried to put the host in
>> > maintenance and once all VMs are moved away to reboot it ?
>>
>> We did so last night. It _did_ fix the issue!
>>
>> Shutting down the VMs on the host, putting the host in and out of
>> maintenance mode did not help. In fact it further illustrated the
>> problem.
>>
>> It took the host from 94% memory used down to 50% memory used, even
>> though there was nothing running on the host at all, and really 99% of
>> memory was available.
>>
>> Rebooting the host resolved the issue.
>>
>> I'm going to apply latest updates to a cluster and see if the issues
>> persist.
>>
>> This therefore sounds like a bug, which is quite bad. Unless there is
>> some communication issue from the engine to the host, which the reboot
>> assists with?
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/QIAWWFRVYTGEAUIBLUA7R7FLCXPTKGQ2/
>>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WI76RKCGU6UEWD3T2O6OSDWHRXW5FFRW/

Reply via email to