Bug 1373020 - Wrong image size after live merge if disk extended
Summary: Wrong image size after live merge if disk extended
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Ala Hino
QA Contact: Natalie Gavrielov
Ala Hino
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-04 20:13 UTC by Ala Hino
Modified: 2017-02-15 15:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-15 15:03:16 UTC
oVirt Team: Storage
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
amureini: devel_ack+
ratamir: testing_ack+

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 63271 0 None None None 2016-09-04 20:15:18 UTC

Description Ala Hino 2016-09-04 20:13:03 UTC 
Description of problem:
Image size (virtual size) is wrong if disk is extended before live merge

How reproducible:
100%

Steps to Reproduce:
1. create a VM
2. add a 1gb block disk
3. create a snapshot
4. extend the disk by 1gb
5. start the VM
6. Delete the snapshot

Actual results:
Virtual size is 1gb, actual size is 2gb

Expected results:
Virtual size is 2gb, actual size is 2gb
Comment 1 Sandro Bonazzola 2016-12-12 14:01:32 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Comment 2 Natalie Gavrielov 2016-12-27 13:00:44 UTC 
Verified, 
rhevm-4.1.0-0.3.beta2.el7.noarch
ovirt-engine-4.1.0-0.3.beta2.el7.noarch
vdsm-4.19.1-1.el7ev.x86_64

Note that when deleting snapshot I get Failed to GetVolumeInfoVDS errors that are related to another issue.
Comment 3 Ala Hino 2016-12-27 13:03:14 UTC 
The exception related to GetVolumeInfoVDS is expected. It is printed after we try to verify that the volume was deleted.

We are planning to remove the exception trace from the log file.
Note You need to log in before you can comment on or make changes to this bug.