+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1418280 +++ ====================================================================== +++ This bug was initially created as a clone of Bug #1415803 +++ Description of problem: Improve logging while performing live merge. Additional info: To verify, following message should be displayed in the vdsm.log (of course with different values): 2017-01-23 19:04:30,873 DEBUG (jsonrpc/5) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Checking job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 (vm:4542) 2017-01-23 19:04:32,193 DEBUG (jsonrpc/5) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 live info {'end': 1409220608L, 'bandwidth': 0L, 'type': 4, 'cur': 1572864L} (vm:4570) 2017-01-23 19:05:07,371 DEBUG (periodic/2) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Checking job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 (vm:4542) 2017-01-23 19:05:07,674 DEBUG (periodic/2) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 live info {'end': 1409417216L, 'bandwidth': 0L, 'type': 4, 'cur': 492175360L} (vm:4570) 2017-01-23 19:05:22,372 DEBUG (periodic/3) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Checking job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 (vm:4542) 2017-01-23 19:05:22,525 DEBUG (periodic/3) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 live info {'end': 1409417216L, 'bandwidth': 0L, 'type': 4, 'cur': 669974528L} (vm:4570) >>> more >>> 2017-01-23 19:06:22,394 DEBUG (periodic/3) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 live info {'end': 1409417216L, 'bandwidth': 0L, 'type': 4, 'cur': 1409417216L} (vm:4570) 2017-01-23 19:06:22,394 INFO (periodic/3) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Starting cleanup thread for job: b321e3ad-5156-4a76-921f-b7a9ed6c68e2 (vm:4587) 2017-01-23 19:06:37,390 DEBUG (periodic/2) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Checking job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 (vm:4542) 2017-01-23 19:06:37,391 INFO (periodic/2) [virt.vm] (vmId='63ad6e6d-76c9-4ab0-a929-8a4a710185ac') Cleanup thread <virt.vm.LiveMergeCleanupThread object at 0x1cb2ed0> successfully completed, untracking job b321e3ad-5156-4a76-921f-b7a9ed6c68e2 base volume 9a07f8c7-65f5-4761-9186-0327eb0fa5d3 top volume 8e5c3593-4042-43e7-a84c-16c482fa8336 (vm:4550) --- Additional comment from Sandro Bonazzola on 2017-01-25 09:56:01 IST --- 4.0.6 has been the last oVirt 4.0 release, please re-target this bug. (Originally by Tal Nisan)
Tested with the following code: ------------------------------------------ ovirt-engine-4.0.7-0.1.el7ev.noarch rhevm-4.0.7-0.1.el7ev.noarch vdsm-4.19.4-1.el7ev.x86_64 Tested with the following scenario: ----------------------------------------- Engine and hosts are running in debug logging mode Created VM with a disk Wrote at least 1g of data to the disk Created snapshot sa1, sa2, sa3, sa4 Delete sa2 - live merge is successful None of the new logs appear in the vdsm.log The same scenario in 4.1.1 does generate the above logs Moving to ASSIGNED! (Originally by Kevin Goldblatt)
Created attachment 1255506 [details] server, vdsm, engine.log Adding logs (Originally by Kevin Goldblatt)
I verified that the tested build does not contain the changes. Looks that this patch is included in 4.19.5 and later builds. Kevin, can you please verify again with a newer build? (Originally by Ala Hino)
I see no problem, Ala is the 3.6.z backport problematic in any way? (Originally by Tal Nisan)
Nope, 3.6.z patch (https://gerrit.ovirt.org/71695) already backported! (Originally by Ala Hino)
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [NO RELEVANT PATCHES FOUND] For more info please contact: rhv-devops
Commit 15e1b6631210382c5d0925dd58d1b4fd3db33a15 (https://gerrit.ovirt.org/#/c/71695/) solves this, although it was submitted with bug 1414067's URL. Moving to ON_QA with v4.17.38 which contains this patch.
Verified with the following code: -------------------------------------- rhevm-3.6.11.1-0.1.el6.noarch vdsm-4.17.39-1.el7ev.noarch Verified with the following scenario: ------------------------------------- Engine and hosts are running in debug logging mode Created VM with a disk Wrote at least 1g of data to the disk Created snapshot sa1, sa2, sa3, sa4 Delete sa2 - live merge is successful None of the new logs appear in the vdsm.log The same scenario in 4.1.1 does generate the above logs Moving to VERIFIED!
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, 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-2017:1824