Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1067432

Summary: Newly created ISCSI thin provision disk reported as preallocated
Product: [Retired] oVirt Reporter: Nikolai Sednev <nsednev>
Component: ovirt-engine-webadminAssignee: Sergey Gotliv <sgotliv>
Status: CLOSED DUPLICATE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4CC: abaron, acathrow, ecohen, gklein, iheim, mgoldboi, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.4.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-23 08:49:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine and vdsm logs none

Description Nikolai Sednev 2014-02-20 13:01:35 UTC
Created attachment 865504 [details]
engine and vdsm logs

Description of problem:
Newly created ISCSI thin provision disk reported as preallocated, while checked via "edit".

Version-Release number of selected component (if applicable):
ovirt-engine-3.4.0-0.7.beta2.el6.noarch
qemu-kvm-rhev-0.12.1.2-2.415.el6_5.4.x86_64
libvirt-0.10.2-29.el6_5.3.x86_64
sanlock-2.8-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Create ISCSI disk as thinprovision at any size, 5Gig will work fine.
2.After disk is created, attach it to VM with OS already installed on it.
3.Do "edit" for the newly attached disk under Disks tab of the particular VM.
4.Yo'll see that disk shown as preallocated instead of being shown as thinprovision.

Actual results:
Newly created thinprovision disk, attached to VM, shown as preallocated instead of being shown as thinprovision.

Expected results:
Newly created thinprovision disk, attached to VM, shown as thinprovision.

Additional info: engine and vdsm logs

Comment 1 Sergey Gotliv 2014-02-23 08:49:16 UTC
This is a duplicate of BZ#1057622

*** This bug has been marked as a duplicate of bug 1057622 ***