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

Bug 1053751

Summary: Alert user of insufficient storage space when VM clone is failed on this issue
Product: [Retired] oVirt Reporter: Allon Mureinik <amureini>
Component: ovirt-engine-coreAssignee: Vered Volansky <vered>
Status: CLOSED CURRENTRELEASE QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4CC: amureini, bugs, ecohen, gianluca.cecchi, gklein, iheim, mgoldboi, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 917682 Environment:
Last Closed: 2014-11-07 14:31:27 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:
Bug Depends On:    
Bug Blocks: 960934    
Attachments:
Description Flags
screenshot none

Description Allon Mureinik 2014-01-15 17:34:49 UTC 
+++ This bug was initially created as a clone of Bug #917682 +++

Description of problem:
If you create a clone from snapshot and if the target SD has not sufficent space, the error message is cryptic

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.2.0-4.fc18.noarch

How reproducible:
always

Steps to Reproduce:
1. create vm
2. create snapshot
3. create clone from snapshot selecting SD with unsufficient space
  
Actual results:
You get a cryptic error
https://docs.google.com/file/d/0BwoPbcrMv8mvaW9OVW84WVI1dkU/edit?usp=sharing

Expected results:

suggest oVirt to at least behave this way:

1) pre-calculate necessary space and in case of problems don't start
the clone operation but open a warning message window to the user impeding it

If during 1) all was ok but in the mean time it went KO (eg unexpected new
storage allocated that made impossible clone completion)
2) notify the user with the actual problem (insufficient space) and
not those crypic messages....
------

The same validation is missing (or at least implemented incorrectly) for cloning a VM from a template
Comment 1 Vered Volansky 2014-06-26 12:27:16 UTC 
Storage validation is now done as part of the bz917682 fix.
Added related patches.

Keeping the bug for the user message issue (point #2 in comment #0), and changing the name accordingly.
Comment 2 Vered Volansky 2014-10-20 12:23:21 UTC 
Created attachment 948526 [details]
screenshot
Comment 3 Vered Volansky 2014-10-20 12:24:29 UTC 
When reproduced the second step, got a good message in the event log:
"Critical, Low disk space. loop domain has 0 GB of free space" .
Attached screenshot, moving to modified.
Comment 4 Allon Mureinik 2014-11-07 14:31:27 UTC 
This patch has included in the build for a LONG while (this the alpha build).
Not sure why the bot missed it, but closing as 3.5.0 has been realesaed