Description of problem: Underscores in node name
(cluster.conf://failoverdomainnode/@name) are accidentally trimmed
because label texts passed to gtk.MenuItem without use_underline parameter.
So if node name includes '_', //clusternode/@name and
//failoverdomainnode/@name in cluster.conf becomes mismatched and
cluster should not work correctly.
Version-Release number of selected component (if applicable):
I confirmed this issue with system-config-cluster in Red Hat Cluster
Suite 4 U5 and RHEL 5 AP.
How reproducible: always
Steps to Reproduce:
1. set node name includes '_' (underscore)
2. select that node in failover domain dialog
'_' in node name (cluster.conf://failoverdomainnode/@name) is trimmed.
Expected results: Not trimmed.
I attach an experimental patch to fix this issue.
Created attachment 237551 [details]
An experimental patch to allow underscores in cluster node names
It's a evident problem of the program and easy to fix although host (node) name
should not contain '_', so I raise the level of severity and priority of this.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~
RHEL 5.5 Beta has been released! There should be a fix present in this
release that addresses your request. Please test and report back results
here, by March 3rd 2010 (2010-03-03) or sooner.
Upon successful verification of this request, post your results and update
the Verified field in Bugzilla with the appropriate value.
If you encounter any issues while testing, please describe them and set
this bug into NEED_INFO. If you encounter new defects or have additional
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.
fix verified in system-config-cluster-1.0.57-3, cluster.conf looks good for nodes with _ in the name.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
*** Bug 488191 has been marked as a duplicate of this bug. ***