Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 159728 - Services does not handle names with multiple words
Summary: Services does not handle names with multiple words
Status: CLOSED DUPLICATE of bug 159681
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-06-07 15:18 UTC by Paul Kennedy
Modified: 2015-04-20 00:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-07 15:38:07 UTC

Attachments (Terms of Use)

Description Paul Kennedy 2005-06-07 15:18:01 UTC
Description of problem:
At the Cluster Configuration tab, creating a new service allows entering
multiple words (with spaces between words) as a name for the service. At the
Cluster Management tab, the service is displayed with no service name, while
other information (State, Owner, Previous Owner, and Restarts) varies according
to the number of words in the service name. Information gets shifted to the
right once for each word in the name. 

Version-Release number of selected component (if applicable):
system-config-cluster 0.9.67

How reproducible:
At the Cluster Configuration tab, create new services with multiple words in
their names, with spaces separating the words. For example, "three word foo".
Save and propagate the cluster configuration, and observe display at the Cluster
Management tab.

Note that running clustat displays the service names as created.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Paul Kennedy 2005-06-07 15:38:07 UTC
Inadvertently refreshed browser page for the original bug, 159681. 

*** This bug has been marked as a duplicate of 159681 ***

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