Bug 1866329 - [CBT] Consume libvirt fix for backup failure after live snapshot with memory of a VM with incremental backups
Summary: [CBT] Consume libvirt fix for backup failure after live snapshot with memory ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.4.3
: ---
Assignee: Eyal Shenitzky
QA Contact: Ilan Zuckerman
URL:
Whiteboard:
Depends On: 1862472
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-05 11:23 UTC by Eyal Shenitzky
Modified: 2020-11-11 06:42 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-11 06:42:35 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)

Description Eyal Shenitzky 2020-08-05 11:23:45 UTC
Description of problem:

When attempting to do an incremental backup after taking a snapshot of the VM with memory fails with "invalid argument: missing or broken bitmap 'testchck' for disk 'vda'".


Version-Release number of selected component (if applicable):
4.4.2_1 master

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with disk
2. Start the VM
3. Create a backup for the VM
4. Create a snapshot with memory for the VM
5. Create an incremental backup for the VM

Actual results:
Incremental backup operation will fail with error -
"invalid argument: missing or broken bitmap 'bitmapname' for disk 'vda'

Expected results:
Incremental backup operation should succeed

Additional info:

Comment 1 Eyal Shenitzky 2020-10-07 10:08:34 UTC
Libvirt contains the fix since version - libvirt-6.6.0-5.el8
So it should be available for testing now.

No code added from our side but we must make sure that this flow works well according to the steps.

Comment 2 Ilan Zuckerman 2020-10-13 08:42:02 UTC
Verified on rhv-4.4.3-8   with   libvirt-6.6.0-6  according to steps from description.

Comment 3 Sandro Bonazzola 2020-11-11 06:42:35 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

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


Note You need to log in before you can comment on or make changes to this bug.