Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 155064 - Cluster MGMT/monitoring doesn't work
Summary: Cluster MGMT/monitoring doesn't work
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster
Version: 4
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-15 21:44 UTC by Corey Marthaler
Modified: 2009-04-16 20:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-29 20:57:12 UTC


Attachments (Terms of Use)

Description Corey Marthaler 2005-04-15 21:44:16 UTC
Description of problem:
I had an up and running cluster, and the MGMT tab showed everybody as up and a
member of the cluster. I then took a node down, waited for cman to notice and
fence it, and remove it from membership. However according to the GUI, nothing
ever happend, all are still considered up and "members"

Version-Release number of selected component (if applicable):
system-config-cluster-0.9.33-1.0.noarch.rpm

Comment 1 Jim Parsons 2005-04-26 11:31:25 UTC
This is fixed, I think, in 0.9.36-1.0...the node and service info is now set to
refresh itself every 5 seconds or so...Unfortunately, I have no cluster to check
this on, so I must rely on QA to test it for me :-(

Comment 2 Corey Marthaler 2005-04-27 21:14:46 UTC
I have verified that the monitoring functionality works for a cman cluster (in
that you can watch from the GUI nodes going in and out of the cluster) however
this functionality is still lacking for a GULM cluster.

Comment 3 Corey Marthaler 2005-04-29 20:57:12 UTC
The GULM functionality now works.


Note You need to log in before you can comment on or make changes to this bug.