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

Bug 1085359

Summary: [engine-backend] Engine reports that disk resize had succeeded although it failed on vdsm
Product: Red Hat Enterprise Virtualization Manager Reporter: Elad <ebenahar>
Component: ovirt-engineAssignee: Allon Mureinik <amureini>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: acathrow, amureini, gklein, iheim, lpeer, Rhev-m-bugs, scohen, yeylon
Target Milestone: ---Flags: amureini: Triaged+
Target Release: 3.4.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: org.ovirt.engine-root-3.4.0-16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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
logs from engine and vdsm + screenshot none

Description Elad 2014-04-08 12:56:15 UTC 
Created attachment 884046 [details]
logs from engine and vdsm + screenshot

Description of problem:
Disk resize is reported as success even though vdsm failed to extend the disk. 
Engine reports that the operation had succeed and that the disk got resized to 0G

Version-Release number of selected component (if applicable):


How reproducible:
When this bug [1] reproduces
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1085338

Steps to Reproduce:
Need to get a situation in which vdsm fails to extend a disk, as reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1085338


Actual results:
2014-04-08 14:48:13,576 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ExtendVmDiskSizeVDSCommand] (org.ovirt.thread.pool-4-thread-26) FINISH, ExtendVmDiskSizeVDSCommand, log id: 20b71ecd
2014-04-08 14:48:13,576 WARN  [org.ovirt.engine.core.bll.ExtendImageSizeCommand] (org.ovirt.thread.pool-4-thread-26) Failed to update VM 7 with the new volume size due to error: VdcBLLException: VdcBLLException: o
rg.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to ExtendVmDiskSizeVDS, error = ecode=1, stdout=[], stderr=['Error resizing image (28)'], message=None, co
de = 100 (Failed with error GeneralException and code 100).VM should be restarted to detect the new size.


In event logs, the disk resize is reported as success (see screenshot attached)

Expected results:
If vdsm fails to extend a disk, engine should report that the operation had failed 

Additional info: logs from engine and vdsm + screenshot
Comment 1 Allon Mureinik 2014-04-23 14:04:07 UTC 
Action Items:
- If a case like this happens, the audit log reported to the user should have a red "X", not a green "V"
Comment 2 Elad 2014-05-12 09:17:27 UTC 
In case disk live resize fails, an appropriate error message is shown to user

" Failed to extend size of the disk '2_Disk1' to 4 GB, User: admin "

Verified using av9
Comment 3 Itamar Heim 2014-06-12 14:11:21 UTC 
Closing as part of 3.4.0