Bug 250498 - RFE: if conga operation results in quorum loss, conga needs to time out eventually
Summary: RFE: if conga operation results in quorum loss, conga needs to time out event...
Status: CLOSED DUPLICATE of bug 239387
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga (Show other bugs)
(Show other bugs)
Version: 5.1
Hardware: All Linux
low
low
Target Milestone: ---
: ---
Assignee: Jim Parsons
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-01 22:03 UTC by Corey Marthaler
Modified: 2009-04-16 22:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-08-09 20:32:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Corey Marthaler 2007-08-01 22:03:48 UTC 
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
Comment 1 Ryan McCabe 2007-08-09 20:32:45 UTC 
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 ***
Note You need to log in before you can comment on or make changes to this bug.