Bug 1740058 - vdsm log contains warnings 'could not run <function <lambda> at 0x7fe0ec1db1b8>'
Summary: vdsm log contains warnings 'could not run <function <lambda> at 0x7fe0ec1db1b8>'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.3.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.4.2
: 4.4.2
Assignee: Tomáš Golembiovský
QA Contact: Tamir
URL:
Whiteboard:
: 1709442 (view as bug list)
Depends On: 1680398 1709442
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 08:31 UTC by Marian Jankular
Modified: 2023-12-15 16:40 UTC (History)
13 users (show)

Fixed In Version: ovirt-engine-4.4.2.1
Doc Type: Bug Fix
Doc Text:
Before this update, when you ran a VM that was previously powered off, the VDSM log contained many uninformative warnings. This update resolves the issue and these warnings no longer appear in the VDSM log.
Clone Of: 1709442
Environment:
Last Closed: 2020-09-23 16:16:06 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3822 0 None None None 2020-09-23 16:16:22 UTC

Description Marian Jankular 2019-08-12 08:31:25 UTC 
+++ This bug was initially created as a clone of Bug #1709442 +++

NOTE:

Customer is experiencing same problems with vdsm-4.20.47-1.el7ev.x86_64 and rhvm-4.2.6.4-0.1.el7ev.noarch


Description of problem:
When running VM that was previously powered off, vdsm log contains many warnings like
(qgapoller/1) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7fe0ec1db1b8> on ['de3f542d-36f3-4758-b667-c2b0b601868f'] (periodic:289)

Version-Release number of selected component (if applicable):
vdsm-4.30.13-1.el7ev.x86_64

How reproducible: always


Steps to Reproduce:
1. run VM
2. when it is up, right click -> Power Off  
3. when it is down, run the VM on the same host

Actual results: vdsm log contains many warnings could not run <function <lambda> ...

Expected results: no warnings


Additional info:
When VM is regularly shutdown, the warnings are not shown.
VM runs ok, no visible problems.
Comment 1 Daniel Gur 2019-08-28 13:15:24 UTC 
sync2jira
Comment 2 Daniel Gur 2019-08-28 13:21:12 UTC 
sync2jira
Comment 3 Marina Kalinin 2020-02-03 21:54:40 UTC 
*** Bug 1709442 has been marked as a duplicate of this bug. ***
Comment 4 Tomáš Golembiovský 2020-06-17 16:33:55 UTC 
This should be fixed in 4.4 by recent changes to the QEMU-GA polling mechanism. Can we move it to QE?
Comment 8 Tamir 2020-08-20 08:50:27 UTC 
Verified on RHV 4.4.2-3. All looks good to me.


Env:
  - Engine instance with RHV 4.4.2-3 and RHEL 8.2.1 installed.
  - Host with RHV 4.4.2-3 and RHEL 8.2.1, vdsm-4.40.25-1.el8ev, ovirt-engine-4.4.2.2-0.3.el8ev


Steps:

1. Create a 4.4 data center and a 4.4 cluster.
2. Install the host, add a storage domain and create a VM.
3. Run the VM and wait for it's status to change to Up.
4. When it is up, right click -> Power Off.  
5. When it is down, run the VM on the same host.

Results (As Expected):
1. A 4.4 data center and a 4.4 cluster were created.
2. The host installed correctly, the storage domain was created and the VM was created.
3. The VM ran without warnings in the VDSM log.
4. The VM was powered off without warnings in the VDSM log.
5. The VM ran without warnings in the VDSM log.
Comment 12 errata-xmlrpc 2020-09-23 16:16:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHV RHEL Host (ovirt-host) 4.4.z [ovirt-4.4.2]), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3822
Note You need to log in before you can comment on or make changes to this bug.