Red Hat Bugzilla – Bug 1441941
VDSM reports pivot complete and engine fails to mark the snapshot to be complete.
Last modified: 2018-05-15 13:43:01 EDT
Description of problem: A snapshot job is selected to be deleted from RHV GUI . It errors on the host end and then completes . The completion never reaches engine and is lost in transmission for which snapshot still shows up . The 2nd issue for snapshot deletion causes stale entries and reports errors as such in engine event logs Message: Failed to delete snapshot '<UNKNOWN>' for VM 'redhatguest'. Version-Release number of selected component (if applicable): ovirt-engine-4.0.3-0.1.el7ev.noarch vdsm-4.18.11-1.el7ev.x86_64 How reproducible: Steps to Reproduce: 1. Create a snapshot 2. Delete the snapshot 3. host errors 1st time for "libvirtError: block copy still active: disk 'vda' not ready for pivot yet" 4. Operation completes and pivots on host end . 5. Engine fails to get this info and snapshot still shows up. Actual results: - The snapshot doesn't complete. - Requires to run it again - Causes stale entries in the command_entities table that keeps retrying the snapshot removal job. Expected results: - Engine waits for the process to complete and marks the snapshot to be complete. Additional info:
Re-opening the bug and marking it as depends on BZ 1438850 that describes the same issue.
(In reply to Ala Hino from comment #5) > Re-opening the bug and marking it as depends on BZ 1438850 that describes > the same issue. Bug 1438850 is already verified. Moving to MODIFIED
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: rhv-devops@redhat.com
verified (Same verification as bug 1509675) Passed automation run with: rhvm-4.2.0.2-0.1.el7.noarch vdsm-4.20.9.1-1.el7ev.x86_64 libvirt-3.2.0-14.el7_4.5.x86_64
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [No relevant external trackers attached] For more info please contact: rhv-devops@redhat.com
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/RHEA-2018:1488