Bug 2211608 - LSM causes discrepancy "Image UUID has a different attribute type on storage(SPARSE) and on DB(PREALLOCATED)"
Summary: LSM causes discrepancy "Image UUID has a different attribute type on storag...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.5.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.5.3-async
: ---
Assignee: Arik
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-01 08:30 UTC by Marian Jankular
Modified: 2023-08-03 11:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Clone Of:
Environment:
Last Closed: 2023-08-03 11:00:24 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 875 0 None open Do not change qcow+preallocated volumes when moving disks 2023-07-18 20:05:44 UTC
Github oVirt ovirt-engine pull 876 0 None open core: do not change qcow+preallocated volumes when moving disks 2023-07-25 08:57:54 UTC
Red Hat Knowledge Base (Solution) 7022817 0 None None None 2023-07-03 11:21:13 UTC

Description Marian Jankular 2023-06-01 08:30:30 UTC
Description of problem:
when moving a block-based preallocated disk with incremental backup enabled (format: COW, type: PREALLOCATED) to another block-based SD it is moved as (format: COW, type: SPARSE)

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

How reproducible:
every time

Steps to Reproduce:
1. move block-based preallocated disk with incremental backup enabled (format: COW, type: PREALLOCATED) to another block-based SD

Actual results:
image is - format: COW, type: SPARSE

Expected results:
the image will be - format: COW, type: PREALLOCATED

Additional info:

Comment 6 Arik 2023-07-17 09:17:26 UTC
Benny, you said it sounds familiar, can you please take a quick look?

Comment 7 Casper (RHV QE bot) 2023-07-18 20:30:25 UTC
This bug has low overall severity and is not going to be further verified by QE.

Comment 8 Arik 2023-07-23 06:20:38 UTC
verification steps:
1. create a VM with a disk that is set with incremental-backup enabled a on storage domain
2. start the VM (not mandatory I think but that's part of the reported issue)
3. verify the disk configuration is qcow+preallocated with (on the host that the VM runs on): vdsm-tool dump-volume-chains <storage domain id> | grep -A3 <image id>
4. move the disk to another block storage domain
5. when the disk movement completes, verify the disk configuration remains qcow+preallocated with the aforementioned command in step 3 (that points to the new storage domain)

Comment 11 Casper (RHV QE bot) 2023-08-03 11:00:24 UTC
This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE.


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