Bug 730619

Summary: StorageDomainCreationError is not specific enough
Product: [Retired] oVirt Reporter: Ken Sugawara <ksugawar>
Component: vdsmAssignee: Tal Nisan <tnisan>
Status: CLOSED EOL QA Contact: Aharon Canan <acanan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.3CC: acanan, amureini, bazulay, bsettle, bugs, gklein, ksugawar, lpeer, mgoldboi, rbalakri, scohen, sgotliv, tnisan, yeylon, ylavi
Target Milestone: m1   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-04 09:32:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
excerpt from vdsm.log containing the offending error none

Description Ken Sugawara 2011-08-15 06:23:57 UTC 
Description of problem:
vdsm does not pass meaningful messages to RHEV-M backend when it fails to add a storage domain.

Version-Release number of selected component (if applicable):
vdsm-bootstrap-4.9-91.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Set up a NFS share on a RHEV hypervisor node
2. Fill up the NFS share (dd if=/dev/zero of=/share/dummyfile ...)
3. With RHEV-M, try to add the share as a storage domain
  
Actual results:
An error dialog indicating "Error 351" but no mention of real reason of failing to add the storage domain. This error message is propagated to RHEV-M from vdsm on the storage node.

Expected results:
An error dialog that indicates what's actually happening (e.g. "No space left on device", etc).

Additional info:
Comment 2 Dan Kenigsberg 2011-08-15 06:43:18 UTC 
Please attach vdsm.log. On the face of it, it does not seem as something that should - or could - make into rhev-3.0.
Comment 3 Ken Sugawara 2011-08-15 06:48:28 UTC 
Created attachment 518228 [details]
excerpt from vdsm.log containing the offending error

Here's an excerpt from vdsm.log that contains the 'No space left on device' error.
Comment 4 Ayal Baron 2012-04-04 15:44:12 UTC 
We won't get to this in 6.3 unfortunately. postponing.
Comment 6 Itamar Heim 2013-12-08 07:46:03 UTC 
still relevant? still planned for 3.4?
Comment 8 Sergey Gotliv 2014-02-23 09:29:03 UTC 
This is the corner case but its still relevant.
Comment 9 Sandro Bonazzola 2015-09-04 09:00:41 UTC 
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.
Comment 10 Ken Sugawara 2015-09-04 09:32:49 UTC 
Closing. If this bug still exists in the latest release, I'll open a new bug.