Hide Forgot
This bug has been copied from bug #682757 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: Losing connection with NFS storage domain used to make future connectStoragePool calls to fail, and switch the host to non-operational state.
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,14 @@ -Losing connection with NFS storage domain used to make future connectStoragePool calls to fail, and switch the host to non-operational state.+Cause: +VDSM lost connection with the NFS storage domain. + +Consequence: +connectStoragePool commands failed, and switched the host to non-operational state. + +Fix: +With this update, disconnecting NFS storage domain does not cause connectStoragePool calls to fail. + +Result: +The host remains functional. + +Text: +When VDSM lost connection with the NFS storage domain, “connectStoragePool” commands failed and rendered the host non-operational. With this update, when the NFS storage domain is disconnected, the host remains functional.
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