1:25 p.m.
No this is on none of my 6 hosts.
/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py
def _qga_call_get_vcpus(self, vm):
try:
self.log.debug('Requesting guest CPU info for vm=%s', vm.id)
with vm.qga_context(_COMMAND_TIMEOUT):
vcpus = QemuGuestAgentDomain(vm).guestVcpus()
except (exception.NonResponsiveGuestAgent,
libvirt.libvirtError) as e:
self.log.info('Failed to get guest CPU info for vm=%s,
error: %s',
vm.id, e)
self.set_failure(vm.id)
return {}
except virdomain.NotConnectedError:
self.log.debug(
'Not querying QEMU-GA for guest CPU info because domain'
'is not running for vm-id=%s', vm.id)
return {}
if 'online' in vcpus:
count = len(taskset.cpulist_parse(vcpus['online']))
else:
count = -1
return {'guestCPUCount': count}
Am 27.12.22 um 12:17 schrieb Arik Hadas:
On Tue, Dec 27, 2022 at 12:52 PM Christoph Timm <ovirt(a)timmi.org> wrote:
No for me with 4.5.4-1.el8
Do you see the same error in the vdsm log?
The stacktrace below suggests that the fix is not included there, see:
https://github.com/oVirt/vdsm/blob/v4.50.4.1/lib/vdsm/virt/qemuguestagent...
Am 27.12.22 um 11:22 schrieb Arik Hadas:
>
>
> On Tue, Dec 27, 2022 at 11:50 AM Christoph Timm <ovirt(a)timmi.org>
> wrote:
>
> Hi Fernando,
>
> I have also from time to time this issue.
>
> I can see the following in the vdsm.log if the issue occurs:
>
> 2022-12-27 10:38:22,473+0100 ERROR (qgapoller/3)
> [virt.periodic.Operation] <bound method
> QemuGuestAgentPoller._poller of
> <vdsm.virt.qemuguestagent.QemuGuestAgentPoller object at
> 0x7fbdf00ced68>> operation failed (periodic:187)
> Traceback (most recent call last):
> File
> "/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py",
> line 185, in __call__
> self._func()
> File
> "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
> line 476, in _poller
> vm_id, self._qga_call_get_vcpus(vm_obj))
> File
> "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py",
> line 797, in _qga_call_get_vcpus
> if 'online' in vcpus:
> TypeError: argument of type 'NoneType' is not iterable
>
>
> This should have been resolved by
> https://github.com/oVirt/vdsm/pull/350
>
>
>
> I had this also in older versions so this is nothing new for me.
> Sometimes I can solve it with putting the host in
> maintenance. But it is coming back after a while.
>
>
> Best regards
> Christoph
>
> Am 19.12.22 um 19:22 schrieb Fernando Hallberg:
>> Hi all,
>>
>> I reinstalled one of the ovirt-nodes, with ovirt-4.5.4, and
>> after the reinstallation the agents of the vms connected to
>> this node cannot communicate with the ovirt-engine.
>>
>> ovirt-engine 4.5.4
>>
>> any idea?
>>
>> VMs work perfectly, but the agent doesn't communicate.
>>
>> Best regards,
>>
>> Fernando Hallberg
>>
>>
>>
>> _______________________________________________
>> Users mailing list --users(a)ovirt.org
>> To unsubscribe send an email tousers-leave(a)ovirt.org
>> Privacy Statement:https://www.ovirt.org/privacy-policy.html
>> oVirt Code of
Conduct:https://www.ovirt.org/community/about/community-guidelines/
>> List
Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/KC...
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LHQSH7AIOPV...
>