This bug has been copied from bug #673835 and has been proposed to be backported to 5.6 z-stream (EUS).
Checked on vdsm22-4.5-63.22.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When asked to mount a non-existing nfs export, vdsm used to return an unknown error code to rhevm. vdsm now returns a comprehensible error code.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,6 @@ -When asked to mount a non-existing nfs export, vdsm used to return an unknown error code to rhevm. vdsm now returns a comprehensible error code.+C: A command to mount a non-existing NFS export path +C: Returned an unknown error code (32) +F: With this update, VDSM returns a comprehensible error code when the command is run +R: StorageServerConnectionError code (451) is returned + +A command to mount a non-existing NFS export path using VDSM returned an unknown error code (32). Now, when this command is run, VDSM returns the StorageServerConnectionError code (451)
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0424.html