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 157338 - "On Member:" hostname doesn't show up on GULM cluster
Summary: "On Member:" hostname doesn't show up on GULM cluster
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-10 18:35 UTC by Corey Marthaler
Modified: 2009-04-16 20:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-05-20 20:12:08 UTC

Attachments (Terms of Use)

Description Corey Marthaler 2005-05-10 18:35:59 UTC
Description of problem:
With a dlm cluster, the "On Member:" field in the MGMT tab shows the hostname of
the machine which the GUI is currently running on. This doens't work on a GULM
cluster, it just has a value of "False", which even that isn't true because the
node is actually a member of the cluster.

Version-Release number of selected component (if applicable):

Comment 1 Jim Parsons 2005-05-17 13:38:26 UTC
There does not seem to be a way of getting current node info from the gulm_tool
like there is from cman_tool, so when on a GuLM style cluster, this field is
hidden. I am calling this a 'fix' because the On Member: field will no longer
display with garbage.

Of course, getHostName could be called, but I think it could be confusing if the
hostname was not the name given to the node in cluster.conf. If this is the
case, then it is an easy fix to add this, but I am reluctant to do so without
consideration from the group to confirm that this approach is correct.

Comment 2 Corey Marthaler 2005-05-20 20:12:08 UTC
calling this fixed then.

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