Description of problem: While using conga to start and stop cluster services on different nodes, I noticed that if a node's service stopping results in a loss of quorum, conga will spin forever telling you to "Please be patient - this cluster's configuration is being modified." There should be some kind of eventual time out that tells the user the cluster is unresponsive due to a quorum loss, that way, the user can fix it either manually or with conga. Version-Release number of selected component (if applicable): luci-0.10.0-3.el5/ricci-0.10.0-3.el5
The same basic problem that causes this behavior is also responsible for bug 239387. Marking as a dupe and adjusting the summary of that bug. *** This bug has been marked as a duplicate of 239387 ***