Hide Forgot
Description of problem: When no nodes can be contacted from within luci server, almost all cluster config tabs (Nodes, Fence Devices, Failover Domains, Service Groups, Configure) return a proper message saying "No nodes from this cluster could be contacted. The status of this cluster is unknown.". Resources tab is an exception to this as it's spitting out an Error 500 with a traceback in logs (see attached below). Version-Release number of selected component (if applicable): luci-0.26.0-21.el6 How reproducible: Always Steps to Reproduce: 1. Create or import a cluster into luci 2. Shutdown all nodes, or cut network access 3. Open https://<luci_node>:8084/cluster/<clustername>/resources Actual results: "Error 500 We're sorry but we weren't able to process this request." Expected results: "No nodes from this cluster could be contacted. The status of this cluster is unknown."
I think this should actually be fixed as a side-effect of fixing Bug 807344
This is now fixed by upstream commit commit 50c49338b7b0d649383872b5f01ae3fde831bbfa Author: Ryan McCabe <rmccabe> Date: Tue Dec 4 09:47:34 2012 -0500 luci: Fix uncaught exception Catch all exceptions when the cluster model cannot be built. Signed-off-by: Ryan McCabe <rmccabe>
Additional fix: commit 04b72fa55081041a79b339ad10ca0d8a582b0256 Author: Ryan McCabe <rmccabe> Date: Fri Dec 7 13:31:14 2012 -0500 luci: Fix for tracebacks when no nodes can be contacted Patch from Radek Steiger <rsteiger> to fix tracebacks that occurred in the fence devices, failover domains, and services sections when no nodes from a cluster cannot be contacted. Signed-off-by: Ryan McCabe <rmccabe>
Fixing this bug shouldn't affect the luci documentation, so I'm marking this as docs_scoped-.
*** Bug 985012 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1603.html