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

Bug 1859403

Summary: VM Disks are all 64MB
Product: [oVirt] ovirt-engine Reporter: Charles Almond <calmond>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.1.8CC: ahadas, bugs, godas, sabose, sasundar, sbose, tnisan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-07 00:10:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screen shots showing the expected and actual configuration none

Description Charles Almond 2020-07-21 23:10:03 UTC
Created attachment 1702009 [details]
Screen shots showing the expected and actual configuration

Created attachment 1702009 [details]
Screen shots showing the expected and actual configuration

Description of problem:
When creating a VM in the admin portal, or when creating a disk directly, the actual size of the disk is always 64MB.  The web front end reports the expected size, but the disk image in gluster is actually 64MB, and the guest OS installer (Linux or Windows) reports the disk as 64MB

Version-Release number of selected component (if applicable):
OVirt 4.4.1.8-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Create disk or VM with disk
2. Try to install guest OS or view image in gluster volume
3.

Actual results:
64MB raw disk image

Expected results:
disk image of configured size

Additional info:
Running on an Adaptec 6805 card on CentOS 8 with latest updates for the nodes.  Gluster hyperconverged setup with replica-3 volume.  Tried thin provision and preallocation.  Tried VirtIO, VirtIO-SCSI, and SATA.  Same results every time.

Comment 1 RHEL Program Management 2020-07-22 07:12:54 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Charles Almond 2020-07-22 12:07:09 UTC
(In reply to RHEL Program Management from comment #1)
> The documentation text flag should only be set after 'doc text' field is
> provided. Please provide the documentation text and set the flag to '?'
> again.

I'm unclear if this is a request for me or an internal comment.  What specifically are you requesting with regards to the doc type?

Comment 3 Arik 2020-07-22 12:11:16 UTC
(In reply to Charles Almond from comment #2)
> I'm unclear if this is a request for me or an internal comment.  What
> specifically are you requesting with regards to the doc type?

You can ignore it.

Comment 4 Charles Almond 2020-07-24 16:15:24 UTC
Additional information: 
Using the Python SDK, I am able to add a new disk to a VM and it is created correctly.  I added a 10G disk to an existing VM this way.
I was also able to make a disk on the CLI using qemu-img and import it using the administrative web interface, and then cloned that disk successfully.

Comment 5 Tal Nisan 2020-07-27 14:16:32 UTC
Sahina,
It seems like it might be Gluster related as our QE did not see it with other storage types, is it an issue you encountered?

Comment 6 SATHEESARAN 2020-08-04 05:39:39 UTC
(In reply to Charles Almond from comment #0)
> Created attachment 1702009 [details]
> Screen shots showing the expected and actual configuration
> 
> Created attachment 1702009 [details]
> Screen shots showing the expected and actual configuration
> 
> Description of problem:
> When creating a VM in the admin portal, or when creating a disk directly,
> the actual size of the disk is always 64MB.  The web front end reports the
> expected size, but the disk image in gluster is actually 64MB, and the guest
> OS installer (Linux or Windows) reports the disk as 64MB
> 
> Version-Release number of selected component (if applicable):
> OVirt 4.4.1.8-1.el8
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> 1. Create disk or VM with disk
> 2. Try to install guest OS or view image in gluster volume
> 3.
> 
> Actual results:
> 64MB raw disk image
> 
> Expected results:
> disk image of configured size
> 
> Additional info:
> Running on an Adaptec 6805 card on CentOS 8 with latest updates for the
> nodes.  Gluster hyperconverged setup with replica-3 volume.  Tried thin
> provision and preallocation.  Tried VirtIO, VirtIO-SCSI, and SATA.  Same
> results every time.

Hello Charles Almond,

Thanks for reporting your issue.

I suspect this issue came out with CentOS 8 QEMU + gluster sharding.
This issue is day1 issue with sharding, which means present in sharding layer from day1,
but got exposed with recent changes in QEMU layer with CentOS 8.

Whatever you see as 64MiB is the shard block size. This issue should be resolved with the patches:
https://review.gluster.org/#/c/glusterfs/+/24471/
https://review.gluster.org/#/c/glusterfs/+/24480/

These fixes got in to the gluster upstream build gluster release-7.7.
This build is tagged to CentOS8 build yesterday (03-Aug) and is now available with 'centos-release-gluster7'.

If you are using ovirt-ng, please wait for the next respin of ovirt-ng and that includes gluster release 7.7

Thanks Charles. Please share your feedback too

Comment 7 Charles Almond 2020-08-07 00:10:45 UTC
The gluster update fixed the problem.  Thanks everyone!