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:
Please attach vdsm.log. On the face of it, it does not seem as something that should - or could - make into rhev-3.0.
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.
We won't get to this in 6.3 unfortunately. postponing.
still relevant? still planned for 3.4?
This is the corner case but its still relevant.
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.
Closing. If this bug still exists in the latest release, I'll open a new bug.