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

Bug 1643112

Summary: The disk size return to 0 GB after resizing in the second time and the extend operation failed
Product: [oVirt] vdsm Reporter: Shir Fishbain <sfishbai>
Component: CoreAssignee: Fedor Gavrilov <fgavrilo>
Status: CLOSED WORKSFORME QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.30.0CC: aefrat, bugs, eshenitz, tnisan
Target Milestone: ovirt-4.3.4Flags: rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-30 07:28:42 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
Attachments none

Description Shir Fishbain 2018-10-25 14:10:36 UTC
Created attachment 1497489 [details]
Attachments

Description of problem:
After removing the large preallocated disk, extend 2 times the thin-provision disk in 1GB, the disk size returns to 0 GB after resizing. The extend operation failed.

Version-Release number of selected component (if applicable):
vdsm version : vdsm-4.20.43-1.el7ev.x86_64
ovirt-engine : ovirt-engine-4.2.7.3-0.1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1) Create a VM with thin-provisioned block-based disk and run the VM.
2) Create a new preallocated disk (that not related to the VM) that fill the block-based storage domain.
4) Start dd operation to the empty thin-provisioned block-based disk.
For 1-4 steps I ran the test case (automation):TestNoSpaceLeftOnStorageDomain
5) When the VM entered to pause mode, shut down the VM.
6) Remove the large preallocated disk.
7) Extend the thin-provisioned block-based disk in 1GB.
8) Extend again thin-provisioned block-based disk in 1GB
*A video of UI attached.

Actual results:
Engine log:
2018-10-22 19:53:55,580+03 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60719) [] EVENT_ID: USER_EXTEND_DISK_SIZE_SUCCESS(371), Size of the disk 'disk_TestNoSpaceLeftOnStorag_2218253120' was successfully updated to 0 GB by admin@internal-authz.
2018-10-22 19:54:45,542+03 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60738) [] EVENT_ID: USER_EXTEND_DISK_SIZE_UPDATE_VM_FAILURE(372), Failed to update VM 'vm_TestNoSpaceLeftOnStorag_2218243336' with the new volume size. VM restart is recommended.
2018-10-22 19:54:45,616+03 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60738) [] EVENT_ID: USER_EXTEND_DISK_SIZE_SUCCESS(371), Size of the disk 'disk_TestNoSpaceLeftOnStorag_2218253120' was successfully updated to 2 GB by admin@internal-authz.
2018-10-22 19:55:25,539+03 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60757) [] EVENT_ID: USER_EXTEND_DISK_SIZE_UPDATE_VM_FAILURE(372), Failed to update VM 'vm_TestNoSpaceLeftOnStorag_2218243336' with the new volume size. VM restart is recommended.
2018-10-22 19:55:25,609+03 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60757) [] EVENT_ID: USER_EXTEND_DISK_SIZE_SUCCESS(371), Size of the disk 'disk_TestNoSpaceLeftOnStorag_2218253120' was successfully updated to 0 GB by admin@internal-authz.

ERRORS from engine log:
2018-10-22 19:53:55,482+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ExtendVmDiskSizeVDSCommand] (EE-ManagedThreadFactory-engine-Thread-60719) [] Failed in 'ExtendVmDiskSizeVDS' method
2018-10-22 19:53:55,492+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60719) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM host_mixed_1 command ExtendVmDiskSizeVDS failed: Command ['/usr/bin/qemu-img', 'resize', '-f', 'qcow2', u'/rhev/data-center/mnt/blockSD/91f13c4f-1f9a-4a86-bad0-951d2f4ac415/images/89673ac8-85a7-439a-9a01-6d7bc01270cc/ca8b1f4b-eda8-49db-b945-c16acd47a92e', '3221225472'] failed with rc=1 out='' err='qemu-img: Failed to grow the L1 table: No space left on device\n'
2018-10-22 19:53:55,492+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ExtendVmDiskSizeVDSCommand] (EE-ManagedThreadFactory-engine-Thread-60719) [] Command 'ExtendVmDiskSizeVDSCommand(HostName = host_mixed_1, ExtendVmDiskSizeVDSCommandParameters:{hostId='bdfb22d5-43fc-4170-b674-b63deb8a60d6', vmId='00000000-0000-0000-0000-000000000000'})' execution failed: VDSGenericException: VDSErrorException: Failed to ExtendVmDiskSizeVDS, error = Command ['/usr/bin/qemu-img', 'resize', '-f', 'qcow2', u'/rhev/data-center/mnt/blockSD/91f13c4f-1f9a-4a86-bad0-951d2f4ac415/images/89673ac8-85a7-439a-9a01-6d7bc01270cc/ca8b1f4b-eda8-49db-b945-c16acd47a92e', '3221225472'] failed with rc=1 out='' err='qemu-img: Failed to grow the L1 table: No space left on device\n', code = 100
2018-10-22 19:53:55,648+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-60719) [] EVENT_ID: USER_FAILED_UPDATE_VM_DISK(89), Failed to update VM vm_TestNoSpaceLeftOnStorag_2218243336 disk disk_TestNoSpaceLeftOnStorag_2218253120 (User: admin@internal-authz).

Expected results:
The size shouldn't be set to 0. 

Additional info:

Comment 1 Sandro Bonazzola 2019-01-28 09:36:38 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 2 Tal Nisan 2019-03-12 10:37:34 UTC
Avihai, this seems to have been solved in bug 1639244, can you please try to reproduce?

Comment 3 Avihai 2019-03-13 09:42:12 UTC
(In reply to Tal Nisan from comment #2)
> Avihai, this seems to have been solved in bug 1639244, can you please try to
> reproduce?

I did the exact same scenario on 4.3.2-0.1.el7 but at my scenario extend did not fail but succeeded and the issue (disk size return to 0 GB after resizing) did not reproduce.

Please close it, for now, If @Shir manage to reproduce it again she will reopen it.